True

False

Either

Neither

Server-side logic only

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

Client-side logic only

In Actions and Variables

Michael has access to Screens with the Registered Role checked.

Michael does not have access to Screens with the Anonymous Role checked.

Michael has access to Screens that have the OrdersAdmin Role checked, but not to Screens with the Registered Role checked.

Michael has only access to Screens that have the OrdersAdmin Role checked.

Yes

No

... must have its Data Type set to Long Integer.

... must be set to Auto Number.

... can only be a single attribute.

... is created automatically and cannot be modified.

True

False

The browser opens.

The OutSystems platform compiles it and generates the HTML, CSS, and JavaScript.

Nothing.

The code is uploaded but only compiled when a user accesses the application.

All input widgets must be inside a Form widget.

You don't need to have a variable. The data typed by the user is saved in the Input widget itself.

It can only be associated to variables of Text data type.

You always need to have a variable to store the value typed by the user.

Screen action to be executed or a screen to navigate to when the value of the element changes.

Screen action to be executed and a screen to navigate to when the value of the element changes.

Use the Max. Records property.

Use the Length value.

Use the Count value.

Use Sorting.

The On Initialize event is triggered before the Screen or Block is rendered and before fetching any data.

The On Initialize event is triggered after the Screen or Block has been rendered, so you can use it to manipulate its structure.

The On Initialize event is triggered after an Aggregate finishes fetching data and can be used to act upon the retrieved data before it's used in the Screen.

The On Initialize event is triggered after the input parameter of a Block changes.

Provide the method's URL, fill the parameter values (if any), test it to get the JSON response, and copy the JSON response to the Body.

Provide the WSDL (the endpoint URL or upload file), choose the binding (if there's more than one), and choose the method to consume.

Enumeration.

Linked lists.

Hash Maps.

Static variables.

changing the Entity B identifier data type to Identifier.

changing the id attribute of Entity B to not be an auto-number and assigning a value to it programmatically, when creating a new record.

adding a new attribute to the Entity B with data type Identifier.

adding a new attribute to the Entity A with data type Identifier.

The Aggregate only returns Orders with Priority, Status and Employee.

The Aggregate returns Orders without Employee and without Status.

The Aggregate returns Orders with Status and at least one Employee.

The Aggregate returns Orders with Priority and with zero or more Employees.

Set the Column to "{EntityName}.[AttributeName]" & define a dynamic sort

Set the Column to "{EntityName}.[AttributeName]" & Automatic add a dynamic sort

Set the Column to "{EntityName}.{AttributeName}" & define a dynamic sort

Set the Column to "{EntityName}.{AttributeName}" & Automatic add a dynamic sort

When using Debugging, it is possible to Inspect information about the value of all variables used at the time of stopping

When using Debugging, it is only possible to Inspect the value of local variables, not inspect the information of Site-property and Session variables.

When using Debugging, it is only possible to Inspect the value of local variables, not inspect the information of the logic being executed.

When using Debugging, Inspect can get information about screen state

True

False

On Consume

On Before Request

On After Response

On REST Request

When the event has Input Parameters.

When the event Input Parameters are all mandatory.

When the Block has Placeholders.

When the Event is set to mandatory.

Text

Integer

Boolean

Date

Run Preparation then render the destination Screen.

Run Screen Action, run Preparation and render the Destination Screen.

Render Destination Screen then run its Preparation.

Run Preparation then run the Screen Action.

The output of the Aggregate will contain all attributes from the Source Entities plus the aggregation columns.

The output of the Aggregate will not include the columns at grey.

We can apply the following functions on attributes of integer data type: sum, max, min, count and average.

We can apply multiple aggregation functions inside an Aggregate.

... create new user Sessions for multiple users at the same time.

... assign the same password to multiple users at the same time.

... grant the access to the same Screens to multiple users at the same time.

... assign and replace a Role to multiple users at the same time.

The Otherwise branch must exist.

Every branch that evaluates to True is executed.

The first branch that the condition evaluates to True is executed.

If no branch evaluates to True, the Otherwise branch is executed.

Ready

Render

Destroy

After Fetch

if the button has Method Navigate.

regardless of the Button's Method.

if the Button has Method Ajax Submit.

if the Button has Method Submit.

Change the Common/Header Web Block, by adding a Container with the new icon. Add the new CSS to the Module Theme's Style Sheet.

Add the new CSS to the Style Sheet of every Web Screens in the application, overriding the Style Sheet of the Common/Header Web Block Replace the Header_Logo with the new icon.

Change the Style Sheet of the Common/Header Web Block, with the new CSS implemented and replace the Header_Logo with the new icon.

Replace the Common/Header Web Block on every Web Screen with a new Web Block containing the new icon and CSS in its Style Sheet.

The two aggregation attributes: ShippingState and Count.

The two aggregation attributes (ShippingState and Count) plus all the attributes of the Source Entity.

Six attributes corresponding to the six visible columns in the Aggregate: ShippingState, Count, Description, DueDate, CreatedOn and Priority.

The two aggregation attributes (ShippingState and Count) plus the columns used to calculate these aggregations.

Decimal, Integer, Long Integer

Long Integer, Integer, Boolean, Entity Identifier(Integer)

Decimal, Long Integer, Boolean, Entity Identifier(Integer)

Decimal, Integer, Boolean, Entity Identifier(Integer)

Bound to a Source Record List

Bound to a Source List

Bound to a Source Record

The Action will end, with sqrt = 0.

The Action will throw an exception and sqrt will have no value.

The debugger will stop in the N < 0 If node.

The debugger will stop at the breakpoint in the End node.

Only inside other Screens.

Only inside other Blocks.

Inside Screens and Blocks, including itself.

Inside Screens and Blocks, except on itself.

Create a third Entity that contains two attributes of types Order Identifier and Product Identifier.

Create a third Entity with a primary key of type Order Identifier and an attribute of type Product Identifier.

Create an attribute of type Order Identifier in the Product Entity and an attribute of type Product Identifier in the Order Entity.

Create an attribute of type Product Identifier in the Order Entity.

A Block improves maintainability, i.e., change the design or functionality, affect all usages.

A Block promotes reusability, i.e. develop once, reuse many times.

A Block encapsulates its own logic.

A Block can only be reused once.

No, there's only one role: Anonymous.

No, there's only one role: Registered.

Yes, Anonymous for unknown users and Registered for users registered in the Users application.