Prepare with OutSystems : Architecture-Specialist-11 exam braindumps as your best preparation materials

OutSystems Architecture-Specialist-11 Exam Overview:

OutSystems Architecture-Specialist-11 Exam Syllabus Topics:

OutSystems Architecture Specialist (OutSystems 11) Sample Questions:

1. Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?

A) Architecture Canvas Modules
B) User Stories, Personas and Roles
C) Information Architecture
D) Integration Technology
E) User Experience Expectations

2. There are generally 4 common style guide scenario. Which of the below is NOT a common style guide scenario?

A) Since the theme is very basic, front-end developer will have to expand and design the theme from there.
Modify Built-in Style Guide: Use when only small changes are required for single application. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, reference that application to the custom Theme and Template.
B) Specialize a Built-in: Use when introducing changes to an existing theme for multiple apps. First, create a custom theme that REFERENCE the Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template
C) Clone a Built-in: Use when introducing extensive changes to existing theme. First, CLONE a custom theme from a Base Theme. Second, clone a Custom Template from the Base Template but this custom theme will reference the custom theme created previously. Third, create new applications based on the Custom Theme and Custom Template.Base Theme can be Outsystems UI or your own custom theme.
D) Built-in Style Guide: Uses Built-in style guide from Outsystems UI. Minor customizations to the Base Theme should be done inside the App Theme.
C, Build Your Own: Use when custom style guide cannot benefit from any existing theme. Just like Clone a Built In scenario, clone both Custom Theme and Custom Template from the Base Theme and Base Template, however clone the Base Theme from Outsystems UI.

3. Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...

A) Same as ECS with local replica but API module is provided. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)
B) ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
C) Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration API. Con: Less impact on source system
D) ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
E) ... a wrapper used to contain the logic, actions and data that will expose code that is inside of O external library or to inspect external database and import the data structures so they can be used as entities inside of OS
F) ... tries to fetch data from local cache entity, if not there, get single entry from the external p system. Cache only that record (read-through caching) Use when whole database too big or costly to synchronize. Integration only touches a small portion of the database. Avoid if access to lists of data is needed up front
G) Same as ECS with local replica but synchronization logic is separated. Pro: Code independence. Consumers of CS is not affected by Sync. Sync can orchestrate several CS
H) ... Entity is not in Outsystems but in an external ERP system. IS just makes remote call to p. external system/database. No data is being kept inside OS. Data retrieval may not be optimized as it needs to traverse two different systems to get the information back. Con: Integration API must support all use cases
I) Same as ECS with direct integration, but through an Enterprise Service Bus
J) ... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

4. _BL module is for

A) Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
B) Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
C) Reusable Core Services with public entities, actions, and blocks.
D) A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.
E) Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

5. There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.

A) Enterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.
B) Independent Apps : Own Menu, Own Login Flow. Login and Menu is defined in the Custom Template. Applications reference to its own Application Theme thus do not use the Login and Menu in the Custom Template.
C) Portal : Common Menu, Common Login Flow. Login and Menu is defined in the Custom Them Application Theme reference the Custom Theme thus have a shared menu and login flow.
D) Intranet (Single Sign On): Own Menu, Common Login Flow. Menu is defined in the Custom Template, but Login is defined in the Custom Theme. Application reference the Custom Them which picks up the Login.

Solutions: