Question 1

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 2

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

Question 3

When should you use the "Commit Transaction" action in OutSystems?

Options :

A : Use it at the beginning of every screen to improve performance

B : Use it to discard changes made during the screen execution

C : Use it to save changes to the database permanently

D : "Commit Transaction" is not a valid action in OutSystems

Answer: C

Question 4

Please select the correct statement:

Options :

A : To change the setting “Internal Access Only” of a WebReference, it’s necessary to open Service Studio and change the setting manually

B : To change the setting “Internal Access Only” of any WebService, you do not need to open Service Studio, just change it in the Service Center

C : From a consumer perspective, the only differences between a Public Action and a Local WebService are the Database Transactions and the Structures

D : From a provider perspective, a Public Action and a Local WebService will generate the same code in the Webserver

Answer: B

Question 5

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

Higher Test Marks with Free Online Professional-Web-Developer Exam Practice

Buying Options: