Free OutSystems Associate-Reactive-Developer Practice Exam with Questions & Answers | Set: 7

All records from the left entity even if there is no match in the right entity (LEFT JOIN).

All records from both Entities (FULL OUTER JOIN).

All records from the right entity even if there is no match in the left entity (RIGHT JOIN).

Only records where there is a match between the two Entities (INNER JOIN).

Client Variables should be used to store confidential information.

Lists or Binary Data can also be stored on Client Variables.

The value of a Client Variable is shared among all logged-in users.

Client Variables are useful to cache frequently accessed information.

TRUE

FALSE

Entity A must have a reference attribute of type Entity B Identifier.

Set the data type of the identifier attribute of Entity B to Entity A Identifier.

Add a new Entity C, with two reference attributes of type Entity A Identifier and Entity B U Identifier.

Entity B must have a reference attribute of type Entity A Identifier.

Only Links can navigate to external URLs.

Links can only navigate to Screens.

Buttons can only have a Screen Action as an On Click Destination.

Links and Buttons can either Navigate to screens or trigger Screen Actions.

A composite key with reference to each parent Entity.

An identifier and foreign keys to each parent Entity.

Foreign keys to each parent Entity and the Count of the junction records.

Id, Label, Order, Is Active.

... the execution is always moved to the Global Exception Handler.

... the execution is moved to all Exception Handlers of the Action.

... a Switch statement is needed to select which Exception Handler will continue the execution.

... the execution is moved to the Exception Handler that is most specific to the Exception.

Server-side logic only

In Actions only (Client-side and Server-Side)

Client-side logic only

In Actions and Variables

All SQL Queries can be replaced by an Aggregate.

Aggregates and SQL Queries have different output types.

Everything that can be define in Aggregate can also be written in a SQL Query.

Both SQL Queries and Aggregates are automatically optimized by the platform.

They cease to be part of output of the Aggregate

They are still part of output of the Aggregate

They are the only columns on the output of Aggregate

It's because they are empty on the database