(Jan-2024) Latest Architecture-Specialist-11 Dumps for Success in Actual OutSystems Certified [Q14-Q30]

NEW QUESTION 14
Which of the below matches the most to Library Module Pattern – Connector Pattern…

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)

… 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

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

… caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

… a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

… tries to fetch data from local cache entity, if not there, get single entry from the external n 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

… is a pattern with two modules, a connector module that can be used to encapsulate an ) external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

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

NEW QUESTION 15
What is NOT a best practice for Mobile Application Architecture: Local Storage?

Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online

Sync on every screen or online event

Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.

NEW QUESTION 16
Which of the below are not recommendations for Architecture Validations

All public entities in Core Modules should be set to Read-only

No business logic in the Foundational Modules

No core entities in Foundational Modules

No screens in the End User Layer

No front-end screens in Core Modules

NEW QUESTION 17
Which of the following is an Assembling principle?

Isolate all business concepts.

Disclose business concepts and integration needs.

Keep concepts with different lifecycles apart.

Join all integrations into a single Module.

NEW QUESTION 18
In which of the following scenarios should you choose to clone a built-in Style Guide?

When minor customizations to the base theme should be done inside the app theme.

It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.

When you want to introduce extensive changes to an existing theme.

When it is not possible to benefit from any existing theme and extensive changes are needed.

NEW QUESTION 19
Which of the below matches the most to Core Module Pattern – Core Entity Pattern…

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.

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

… tries to fetch data from local cache entity, if not there, get single entry from the external 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

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

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

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)

… a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

… caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

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

… Entity is not in Outsystems but in an external ERP system. IS just makes remote call to 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

NEW QUESTION 20
In the Architecture Canvas, where should the API module sit in?

Core Layer

End-User Layer

Foundation Layer

NEW QUESTION 21
ISO/IEC 9126:1991 included several different dimensions. Which is NOT part of ISO/IEC 9126:1991?

Usability : Usability from the point of view of the users

Efficiency : Efficiency which relates to the performance to the amount of resources used

Portability : Portability which defines the ability to move software between environments

Security : Security which relates to the strength of the of the software against cybersecurity attacks

Reliability : Reliability which ensures that a software solution can maintain it performance over a period of time

Maintainability : Maintainability which relates to the effort needed to make modifications

Functionality : Functionality as a set of functions that satisfy needs

NEW QUESTION 22
Considering Discovery, which of the following sentences is FALSE?

Discovery automatically assigns a module to an Architecture Canvas layer, following the module’s naming convention.

Discovery only validates architecture rules at the module level.

Discovery allows you to determine for every module, which elements are being consumed by other modules.

Discovery cannot categorise modules to domains

NEW QUESTION 23
Which of the below is not part of the Architecture Validation

No Downward References To Foundation Modules

No Side References Between End-User Modules

No Circular References

No Upward References

NEW QUESTION 24
Which of the below matches the most to Core Module Pattern – ECS with Isolated Synchronization Logic Pattern…

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

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

… 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

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

… caches only summary data that is frequently lister, joined or searched. Full detail for a O single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

… 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

… tries to fetch data from local cache entity, if not there, get single entry from the external v 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

… is a pattern with two modules, a connector module that can be used to encapsulate an ) external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.

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)

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

NEW QUESTION 25
_Th module is for

to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).

technical wrapper to consume and normalize an external service.

Theme, look & feel elements, menu, etc.

Generic Library module.

Reusable UI Patterns for layout and display only – no Business logic.

NEW QUESTION 26
Which of the below matches the most to Core Module Pattern – ECS with Local Replica Pattern…

… 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

… 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.
p 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

… a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS

… caches only summary data that is frequently lister, joined or searched. Full detail for a single entry is fetched directly from external system. Use when whole database too big or costly to synchronize. Details are only required for single entities (not lists)

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

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

… tries to fetch data from local cache entity, if not there, get single entry from the external 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

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

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)

NEW QUESTION 27
Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.

Don’t join concepts with different lifecycles

Apply known design patterns

N/A

Join conceptually-related concepts

Isolate reusable logic from Integration logic

NEW QUESTION 28
OAPI is different compared to API. What is inside an OAPI?

Service Action

REST API

NEW QUESTION 29
What is a best practice for Mobile Application Architecture: Local Storage?

Do not use local storage(mobile device), instead try to use central storage(server side)

Map server side static entities into local entities

Have a local storage inside the CS Module instead of M_CS Module

Use a centralized local storage for all mobile applications to ensure maintainability

NEW QUESTION 30
Which of the below is NOT a Synchronization Best Practice for mobile application?

Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server

Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction

Sync only when strictly required
E Don’t sync on every screen or online event

Only synchronize relevant data

Do not use Entity Bulk Operation to ensure small lightweight updates

Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

(Jan-2024) Latest Architecture-Specialist-11 Dumps for Success in Actual OutSystems Certified [Q14-Q30]

Leave a Reply Cancel reply

Architecture-Specialist-11 Practice Tests

Related Certifications

Recent Posts

Categories

Archives