Question 1

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 2

If you have a screen that is slow to show to the user, what should you do to speed it up?

Options :

A : Replace any complex queries in preparation by aggregates and cycles to process their results.

B : Do all the pre-processing during preparation to speed up operations when calling screen actions

C : Replace all aggregates and queries by server actions that will process the information and return the results.

D : If possible, avoid doing any query results processing during preparation, delaying these tasks to any write operations

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

Your OutSystems application needs to handle user feedback and ratings. How would you design and implement a user-friendly feedback system with considerations for data storage and analysis?

Options :

A : Ignore user feedback for simplicity.

B : Leverage External Database Entities for storing feedback and use Aggregates for analysis.

C : Use only built-in forms for feedback.

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