Associate-Reactive-Developer OutSystems Associate Reactive Developer (OutSystems 11) Exam Free Practice Exam Questions (2025 Updated)

Basic, Complex, and Record

Basic, String, and Object

Basic, Structure, Entity, and List

Basic and List only

When you press the Submit button, you will perform the webpage B's preperation, then build the webpage of the webpage B, then perform the screen action of the Submit button.

When clicking the Submit button, it will perform the screen action of the Submit button, then perform the preperation of the webpage B and then build the webpage screen B

When the Submit button is pressed, perform the screen action of the Submit button and then build the screen of webpage B, the webpage's preperation will not be performed.

When clicking Submit button, it will immediately perform preperation of webpage B and then build screen of webpage B, screen action of Submit button will not be performed.

A Form groups input widgets and allows displaying and editing data.

A Form is useful to validate data submitted by the user.

A Form has a Source property that will hold the values submitted by the user.

Besides input widgets, a Form can hold other widgets such as Links and Buttons.

True

False

Either

Neither

It makes a copy of the Template to create the screen with sample data that cannot be replaced.

It makes a copy of the Template to create the screen with sample data that can be replaced by real data.

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.

True

False

In action handle On Notify of List Navigation can not execute refresh List Navigation.

In action handle On Notify of List Navigation can not execute Refresh Table.

In action handle On Notify of List Navigation can not execute Refresh Query

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.

Decide what widgets will be rendered.

Fetch data from databases.

Submit the form data to the server.

Redirect the user to the proper screen.

When adding the output of Server action, the consumer will get an error if the Producer is not updated

When changing the internal logic of a server action without changing the input-output, Consumer still uses the latest logic

When deleting the input of the Server action, the consumer will get an error if the Producer is not updated

When changing the content of the web screen, the Consumer is still not affected even without updating Producer

True

False

Neither

Either

Is a navigator for a Table Records with multiple pages, showing a defined number of elements per page.

Is a navigator for a Form with multiple pages, showing a defined number of elements per page.

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.

Manipulate the DOM.

Set the default value of a Local Variable.

Act on data returned by a Data Action.

Retrieve data from the server database.

Local Variables allow temporarily storing relevant information inside a Screen.

Input Parameters allow passing data between Screens when navigating between them.

When the value of a Local Variable changes the user interface reacts immediately.

Local Variables from a Screen may be directly accessed from another Screen.

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).

Username.

Password.

Search filter keyword.

ID of a user session.

Elements can be exposed and reused, but only within the same application.

A Module that reuses an element from another Module is called a Consumer.

An application is composed of a set of Modules.

Modules can be of different types, such as Reactive Web App, Blank, or Extension.