Outsystems Becoming a Reactive Web Developer Path
questions with verified answers
A __ reserves space in the interface to be allocated when the block is
instantiated Ans✓✓✓ placeholder
A Block can be used Inside Screens and Blocks, except Ans✓✓✓ on
itself
A Block can be used...
A. Only inside other Screens.
B. Inside Screens and Blocks, including itself.
C. Inside Screens and Blocks, except on itself.
D. Only inside other Blocks. Ans✓✓✓ C.
A developer should favor using a Structure instead of the Entity in the
output of a SELECT SQL Query. Do you agree with this statement?
A. Yes, because queries become easier to maintain.
B. Yes, because queries will retrieve fewer Attributes and less data.
C. No, since it is exactly the same.
D. No, it is preferable to use the Entity instead of the Structure.
Ans✓✓✓ B.
,About Roles, All application users have the "Registered" Role. Ans✓✓✓
TRUE
About Roles, It is necessary to create Role Anonymous for new
applications. Ans✓✓✓ FALSE
About Roles, Roles are used to control user access exclusively through
the "Roles" property of pages. Can set widgets also with IF''s Ans✓✓✓
FALSE
About Roles, Roles cannot be shared between modules. They Can...
Ans✓✓✓ FALSE
About Site Properties, Supports basic data types, entity identifiers and
lists... NO LISTS Ans✓✓✓ FALSE
About Site Properties, The values are never reset. Ans✓✓✓ TRUE
About Site Properties, The values are the same for all users of the
system. Ans✓✓✓ TRUE
About Site Properties, They can be modified through the Service
Center. Ans✓✓✓ TRUE
,About Web Services, Documentation is automatically generated for
SOAP and REST API's services. Ans✓✓✓ FALSE
About Web Services, For SOAP services, the contract formalized in a
WSDL file is generated. Ans✓✓✓ TRUE
About Web Services, It is possible to consume and expose SOAP and
REST API's services using OutSystems. Ans✓✓✓ TRUE
About Web Services, Requests and responses to SOAP services have
XML format. Ans✓✓✓ TRUE
access control for roles in Outsystems (3): Ans✓✓✓ define the user,
grant a role to a user, define/check permissions
Aggregates allow hiding columns to reduce the number of attributes
returned in the query... Ans✓✓✓ FALSE
Aggregates allow to visually add filters to a query... Ans✓✓✓ TRUE
Aggregates allow us to define database queries in a visual way by
Ans✓✓✓ adding Sources, creating Filters, defining Sorting
, Aggregates can be defined at the Screen level because widgets have
access to the... Ans✓✓✓ output data of Aggregates
Aggregates have a Fetch property with 2: Ans✓✓✓ At Start, Only on
demand
Aggregates have a List as output that type matches the definition of the
query...... Ans✓✓✓ TRUE
Aggregates have two Fetch properties: Ans✓✓✓ At Start, Only On
Demand
Aggregates support calculated attributes over multiple attributes...
Ans✓✓✓ TRUE
Aggregates with Fetch property set to Only on demand do not run
when... Ans✓✓✓ screen is initializing, needs to be triggered
programmatically
All logged in end-users have the Ans✓✓✓ Registered role
An Entity Identifier ... can only be a single attribute. Ans✓✓✓ TRUE
questions with verified answers
A __ reserves space in the interface to be allocated when the block is
instantiated Ans✓✓✓ placeholder
A Block can be used Inside Screens and Blocks, except Ans✓✓✓ on
itself
A Block can be used...
A. Only inside other Screens.
B. Inside Screens and Blocks, including itself.
C. Inside Screens and Blocks, except on itself.
D. Only inside other Blocks. Ans✓✓✓ C.
A developer should favor using a Structure instead of the Entity in the
output of a SELECT SQL Query. Do you agree with this statement?
A. Yes, because queries become easier to maintain.
B. Yes, because queries will retrieve fewer Attributes and less data.
C. No, since it is exactly the same.
D. No, it is preferable to use the Entity instead of the Structure.
Ans✓✓✓ B.
,About Roles, All application users have the "Registered" Role. Ans✓✓✓
TRUE
About Roles, It is necessary to create Role Anonymous for new
applications. Ans✓✓✓ FALSE
About Roles, Roles are used to control user access exclusively through
the "Roles" property of pages. Can set widgets also with IF''s Ans✓✓✓
FALSE
About Roles, Roles cannot be shared between modules. They Can...
Ans✓✓✓ FALSE
About Site Properties, Supports basic data types, entity identifiers and
lists... NO LISTS Ans✓✓✓ FALSE
About Site Properties, The values are never reset. Ans✓✓✓ TRUE
About Site Properties, The values are the same for all users of the
system. Ans✓✓✓ TRUE
About Site Properties, They can be modified through the Service
Center. Ans✓✓✓ TRUE
,About Web Services, Documentation is automatically generated for
SOAP and REST API's services. Ans✓✓✓ FALSE
About Web Services, For SOAP services, the contract formalized in a
WSDL file is generated. Ans✓✓✓ TRUE
About Web Services, It is possible to consume and expose SOAP and
REST API's services using OutSystems. Ans✓✓✓ TRUE
About Web Services, Requests and responses to SOAP services have
XML format. Ans✓✓✓ TRUE
access control for roles in Outsystems (3): Ans✓✓✓ define the user,
grant a role to a user, define/check permissions
Aggregates allow hiding columns to reduce the number of attributes
returned in the query... Ans✓✓✓ FALSE
Aggregates allow to visually add filters to a query... Ans✓✓✓ TRUE
Aggregates allow us to define database queries in a visual way by
Ans✓✓✓ adding Sources, creating Filters, defining Sorting
, Aggregates can be defined at the Screen level because widgets have
access to the... Ans✓✓✓ output data of Aggregates
Aggregates have a Fetch property with 2: Ans✓✓✓ At Start, Only on
demand
Aggregates have a List as output that type matches the definition of the
query...... Ans✓✓✓ TRUE
Aggregates have two Fetch properties: Ans✓✓✓ At Start, Only On
Demand
Aggregates support calculated attributes over multiple attributes...
Ans✓✓✓ TRUE
Aggregates with Fetch property set to Only on demand do not run
when... Ans✓✓✓ screen is initializing, needs to be triggered
programmatically
All logged in end-users have the Ans✓✓✓ Registered role
An Entity Identifier ... can only be a single attribute. Ans✓✓✓ TRUE
