Question 1

Select the correct statement regarding the differences between a “Submit” and an “Ajax Submit”

Options :

A : Even though the Preparation is executed in both methods, the Ajax Submit request is made through Javascript, avoiding the browser to hang while waiting for an answer

B : The Ajax Submit request is executed asynchronously and allows to refresh only parts of the screen, however the server-side logic doesn’t have access to all contents previously loaded during the Preparation

C : There are no differences between both platform methods, they both implement the HTTP POST method

D : None of the above

Answer: B

Question 2

Regarding Roles, choose the correct option:

Options :

A : - System role Registered is granted to any authenticated user

- Web Screens and Human Activities can be associated to Roles at run time

B : - Roles are used to design your security policies and associate them with eSpace elements and end-users

- Roles can only be associated to users through the Users application

C : - A role defined in one eSpace can be used in another eSpace

- When eSpace MyApp is created, system role MyAppUser is automatically created and can't be deleted

D : - eSpace elements that can be associated to Roles, include Web Screens and Human Activities

- Applications can use GrantRole and RevokeRole actions to manage role association to users

Answer: D

Question 3

In OutSystems, can asynchronous processes interact with the database?

Options :

A : Asynchronous processes cannot interact with the database

B : Yes, asynchronous processes can read and write to the database

C : Database interactions are automatically handled by OutSystems and not relevant for asynchronous processes

D : Asynchronous processes can only read from the database but not write

Answer: B

Question 4

What is the purpose of the "Wait" action in asynchronous logic?

Options :

A : To introduce a delay in the execution of asynchronous logic

B : Wait action automatically pauses the Timer until manually resumed

C : To wait for user input in asynchronous processes

Answer: A

Question 5

When using Expand Inline parameters in SQL queries, which of the following is not a best practice?

Options :

A : All options are bad practices.

B : Build WHERE column IN (@values) clauses by wrapping all the values in a EncodeSql call: values =

EncodeSql(name1 + "," + name2 + "," + name).

C : Perform manual string encoding using the Replace function.

D : Use EncodeSql to encode the full contents of an SQL parameter. For example: myparameter = EncodeSql("WHERE surname = " + @myVariable1 + " OR name = " + @myVariable2)

Answer: A

Free Professional-Web-Developer Mock Exam – Practice Online Confidently

Buying Options: