In an Aggregate, the Sources section is used for...

• A.Defining conditions to get specific subsets of records.
• B.Defining the order of the Aggregate's output records.
• C.Defining values for testing the Aggregate's output records.
• D.Defining the Entities we want to retrieve records from.

Comment: *

Name: *

Email: *

Verification: *

Inside an Action flow...

• A.*** only one Exception Handler may exist.
• B.*** the Exception Handler flow can!t intersect other flows.
• C.*** it's mandatory to have at least one Exception Handler.

Comment: *

Name: *

Email: *

Verification: *

The lifecycle of a User Session...

• A.Starts when the user authenticates in the application and ends with a logout or a timeout.
• B.Starts when the user authenticates in the application and never ends.
• C.Starts on the first access to the application (even if anonymous) and ends with a logout or a timeout.
• D.Starts on the first access to the application (even if anonymous) and never ends.

Comment: *

Name: *

Email: *

Verification: *

In any case, should use Site property

• A.Minimum password length
• B.Number of logged user
• C.Search field value

Comment: *

Name: *

Email: *

Verification: *

Consider the following Server Action. What happens if the GetEmployeeById (https://drive.google.com/file/d/1Q5JfXEu9L5OsY017HLrMbI8ZIsRl8BJ3/view?usp=sharing) Aggregate does not return any record?

• A.No exception flow is executed.
• B.The RecordNotFound flow is executed.
• C.The DatabaseException flow is executed.
• D.The module's global exception handler is executed.

Comment: *

Name: *

Email: *

Verification: *