Question No. 1

What is NOT a best practice for Mobile Application Architecture: transactions & granularity?

AHave long synchronizations in a single transaction. Better UX as app does not need to sync all the time. Is prepared for constant offline or device standby

BEnsure order and sync granularity. Sync incrementally by entity with partial commit. This way O synchronizations is prepared for constant interruptions and allow retries without repeating the entire synchronization from the start.

Show Answer

Correct Answer: A

Question No. 2

Elements such as the menu and login can be shared across different apps. In the menu and login are defined inside the theme. Which use case is this?

APortal

BIntranet

CIndependent Apps

Show Answer

Correct Answer: A

Question No. 3

The Architecture Design Process has three steps. Which of the options below is NOT one of those steps?

AOrganize

BPlan

CAssemble

DDisclose

Show Answer

Correct Answer: B

Question No. 4

What is Application Composition Process?

AAnswer is the above.

BProcess to package modules into apps

Show Answer

Correct Answer: B

Question No. 5

Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation

ASame 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

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

CSame 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

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

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

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

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

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

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

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

Show Answer

Correct Answer: B

Free OutSystems Architecture-Specialist-11 Exam Actual Questions

The questions for Architecture-Specialist-11 were last updated On Jan 17, 2025