OutSystems Architecture Specialist (OutSystems 11) Architecture-Specialist-11 Prüfungsfragen mit Lösungen:
1. Which of the following Data elements can we find in a End-User layer Module?
A) CRUD actions for Entities
B) Core Entities (exposed as read-only)
C) Entities to save UI states
D) Non-core Entities
2. Considering Architecture Dashboard(AI Mentor), which of the following sentences is FALSE?
A) Architecture Dashboard performs a code analysis that uncovers patterns related to performance, security, architecture and maintainability.
B) Architecture Dashboard allows you to automatically apply a solution to solve a found code pattern.
3. Foundation may have non-business services and business services in them
A) FALSE
B) TRUE
4. Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
A) 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
B) ... 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
C) 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)
D) ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
E) ... 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
F) 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
G) ... 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.
H) ... 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)
I) ... a wrapper used to contain the logic, actions and data that will expose code that is inside of i external library or to inspect external database and import the data structures so they can be used as entities inside of OS
J) ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
5. What is NOT a best practice for Mobile Application Architecture: transactions & granularity?
A) Have 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
B) Ensure 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.
Fragen und Antworten:
| 1. Frage Antwort: C | 2. Frage Antwort: B | 3. Frage Antwort: A | 4. Frage Antwort: B | 5. Frage Antwort: A |
1285 Kundenbewertungen
