Associate-Reactive-Developer Sample Questions Answers

If a = b then Action C execute

If a <= b then Action C execute

If a < b then Action B execute

If a <= b then Action B execute

It promotes re-usability, i.e. develop once, reuse many times.

It encapsulates its own logic.

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

It can only be reused once.

Change the Join between the Order and the Priority to Only With and create a Count over the Priority.Id attribute.

Create a Group By over the Priority.Id attribute and a Count over the Order.Id attribute.

Create a GroupBy over the Order.Id attribute and a Count over the Priority.Id attribute.

Remove the Join between the Order and the OrderStatus and create a Count over the Priority.Id attribute.

If the data submitted by the user matches the data type of the variables associated with the respective Inputs.

If the Mandatory fields are filled in and if the data submitted by the user matches the data type of the variables associated Inputs.

If the Mandatory fields are filled in.

If the data submitted by the user matches the data type of the Source Record of the Form.

Ready

Render

Destroy

After Fetch

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.

The hidden columns help optimizing the Aggregate.

Columns that are empty in the database are automatically hidden.

The hidden columns are not part of the output.

Hiding columns in the Aggregate only affects the preview of the output.

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.

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.

You use the Popup_Editor_Close to close the Popup, followed by the Ajax Refresh to refresh the Source Screen.

You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen, followed by the Popup_Editor_ ... the Popup

You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen and close the Popup.

You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen, followed by the Popup_Editor__... the Popup and an Ajax Refresh to refresh the Source Screen.

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.

1-to-Many and Many-to-Many.

1-to-1, 1-to-Many, and Many-to-Many.

1-to-1 and 1-to-Many.

Many-to-Many.

Profile Picture

User Name

User Identifier

Credit Card Number

The Ajax Refresh is ignored.

The whole screen is refreshed.

The Web Block Preparation is executed and the Web Block updated.

The Web Block stays the same because the Preparation is not executed.

Text

Integer

Boolean

Date

.. all Screens are created that way even in Blank modules.

all Screens must have a Header, Menu and Footer,

it is built with a layout Web Block, that has placeholders for those Web Blocks.

all Screen have three Containers for those Web Blocks.

The Max Records property of the Pagination holds the number of records to show per page.

The Start Index property of the Pagination holds the current page number.

The Total Count input of the Pagination pattern should be set to the number of records per U page.

... only one Exception Handler may exist.

... it's mandatory to have at least one Exception Handler.

... the Exception Handler flow can't intersect other flows.

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.

Functions can be used inside the Condition of an If.

Only one of the branches is shown at runtime.

Multiple widgets may be added inside each branch.

More branches may be added to an If Widget.

A Module, a UI Flow, or an individual Screen or Web Block.

A Module, a UI Flow, or an individual Screen.

A Module or a UI Flow.

Only the Module.

Any data type can be used.

Basic and Structures Types.

Basic and Entity Identifier Types.

Basic and Entity Types.

True

False

Mandatory values, correct Data Types, and Business Rules.

Mandatory values and correct Data types.

Correct Data Types and Business Rules.

Mandatory values and Business Rules.

Allows sorting by column in a Form by clicking on that column.

Allows sorting by column in a Table Records by clicking on that column.

True

False

Either

Neither

True

False

TRUE

FALSE

Only displays static images.

Only displays images given by a URL.

Only displays images stored in the database.

Displays static images, images in a URL, and images in the database.

TRUE

FALSE

Reference attribute - Primary Key.

Index - Index.

Entities - Tables.

Attributes - Column.

Screen Aggregates can only be executed when explicitly called.

Screen Aggregates can only fetch data from the database.

Screen Aggregates only exist within the scope of the Screen where they were defined.

Screen Aggregates run asynchronously and in parallel.

Links can only Navigate to Screens.

Buttons can only Submit requests.

Links and Buttons can either Navigate to screens or Submit requests.

Links and Buttons can only Navigate to screens.

False

True

Both True and False branches are mandatory.

If statements can also be used to implement ad-hoc loops.

Only one of the branches is executed, depending on the If condition's outcome.

More branches may be added if needed.

TRUE

FALSE

The On Parameters Changed must be explicitly triggered by the parent of the Block

If the value of a Block Input Parameters changes inside a Client Action of the Block.

When the parent of the Block changes the value of at least one of the Block Input Parameters.

Refresh the data of a specific query is present in the Preparation.

Refresh the data of all queries in the Preparation.

Run the Preparation again.

Refresh a specific widget.

a Screen Action runs with the data from the Form as Input parameter.

.. the Preparation runs then the Screen Action runs.

. the data is stored in the Form's Record implicit variable.

. the data in the Form is only available in the Preparation.

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

Decide what widgets will be rendered.

Fetch data from databases.

Submit the form data to the server.

Redirect the user to the proper screen.

False

True

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.

A Static Entity always has only 4 attributes Id, Label, Order, Is_Active

A Static Entity has the functions Create, Update, Get

A Static Entity can add attributes with the basic data type and identifier data type of all other entities.

A Static Entity can add attributes with the basic data type and the identifier data type of other static entity.

TRUE

FALSE

Ready

Render

Destroy

After Fetch

Ready

Render

Destroy

After Fetch

When the web block is in one screen, the parent screen is required to have a screen action to handle the event of the child web block, but the case is in another web block.

When the web block is in a web block, the parent web block is required to have a screen action to handle the event of the child web block, but the case is in another screen.

When the web block is in one screen or another web block, the parent screen or web block is required to have a screen action to handle the event of the child web block.

When the web block is in one screen or another web block, the parent screen or web block is not required to take action to handle the event of the child web block.

REST Web Service API Key

Total Stock Quantity of Products

Current user ID

Search Keyword

PUT

POST

GET

PATCH

Web Block can only have 1 output

Web Block cannot have preparation action

Web Block can Preparation action

Web Block can have multiple outputs

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.

Color.Id

GetColors.Color.Label

Color

Color.Label

DeleteCustomer.

UpdateCustomer.

CreateCustomer.

RetrieveCustomer.

A Placeholder reserves space in the interface to be allocated when the block is instantiated.

Placeholders can be added to Screens and Blocks.

When a Block with Placeholders is instantiated, it is mandatory to place at least one widget inside the placeholders.

Only one placeholder may be added per Block.

Insert, Update, Delete

Create, CreateOrUpdate, Update, Get, GetForUpdate, Delete

GET, POST, DELETE

Add, Change, Remove

Filters are concatenated with the AND operator.

A record is included in the output if it matches at least one of the filters.

Logical operators and some built-in functions can be used inside filters.

All filters are translated to SQL and included in the WHERE clause.

Custom validations are checked on the server-side if all mandatory fields are empty.

Built-in validations are first checked on the client-side and, if not valid, the user gets error messages immediately.

Built-in validations are first checked on the client-side but the request goes to the server anyway to perform custom validations.

There is no Client & Server validation.

Never.

When the input parameter (N) is less than zero.

When the input parameter (N) is zero.

When the input parameter (N) is greater than zero.

When the User Request web page, when pressing the button (with method Submit)

When the User Request web page, when pressing the button (with method Ajax Submit)

Service Center

Integration Studio

Service Studio

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.

5

6

7

8

On Consume

On Before Request

On After Response

On REST Request

True

False

Varies depending on the module setup

Varies when using function.

Entity.Attribute

{Entity}.[Attribute]

[Entity].{Attribute}

(Entity).{Attribute}

It can't be extended with any new attributes.

It has two Entity Actions.

It can't be changed after the first publish.

It contains a set of Records.

True

False

••• one or more Start nodes but only one End node.

••• only one Start node and one End node.

••• only one Start node but multiple End nodes.

... multiple Start and End nodes.

True

False

Right-click on the widget and select Import Data from Entity

Delete the widget and create it again with the right Entities.

Drag your Entity and drop it onto the widget.

Right-click on the Entity and select Import Data from Excel.

Ready

Render

Destroy

After Fetch

Expression can call server action and use the server action output to calculate

If the expression is empty, the value shown in the Example property will be displayed

The value of Expression will be calculated during the build screen and displayed on the screen

Expression cannot call server action and uses server action output to calculate

Special List

Events

On Refresh

On Click or On Change, depending on the widget.