OutSystems Certified Architecture-Specialist-11 Dumps Questions Valid Architecture-Specialist-11 Materials
Current Architecture-Specialist-11 Exam Dumps [2024] Complete OutSystems Exam Smoothly
NEW QUESTION # 11
Which of the below matches the most to Core Module Pattern - Core Entity Pattern...
- A. ... 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)
- B. 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
- 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. ... 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
- E. ... 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
- F. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- G. ... 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
- H. 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
- I. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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.
Answer: I
NEW QUESTION # 12
_API module is for
- A. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- B. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- C. Reusable Core Services with public entities, actions, and blocks.
- D. 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.
- E. 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.
Answer: A
NEW QUESTION # 13
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?
- A. It identifies possible performance bottlenecks.
- B. It minimizes the impact of changes.
- C. It optimizes lifecycle independence.
- D. It promotes a correct abstraction of reusable services.
Answer: A
NEW QUESTION # 14
Which of the below matches the most to Core Module Pattern - ECS with Local Replica Pattern...
- A. ... 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 - 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)
- 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. ... 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
- E. ... 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
- F. ... 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
- G. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- H. 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
- I. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
Answer: E
NEW QUESTION # 15
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Reveal nature of each module
- B. Normalize known patterns
- C. Enforce the reference architecture
- D. Ensure it belongs to the correct layer
Answer: D
NEW QUESTION # 16
Which of the below is NOT a reason for Validating a Modules' Architecture?
- A. Minimizes impact of changes
- B. Promotes microservices
- C. Avoid poor service abstraction
- D. Optimizes lifecycle independence
- E. Promotes abstraction of reusable services
- F. Prevent slow deployments, inflexible legacy systems
- G. Stop unmanageable dependencies
Answer: B
NEW QUESTION # 17
What does NOT happen due to a lack of architecture concerns?
- A. Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
- B. Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
- C. Inflexible and slow-moving legacy systems : adapting legacy systems to business changes may be difficult. Changes in complex and inflexible systems can take a long time
- D. Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
Answer: B
NEW QUESTION # 18
Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
- A. ... 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
- B. 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
- C. ... 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
- D. ... 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.
- E. 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)
- F. ... 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
- G. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- H. 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
- I. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- J. Same as ECS with direct integration, but through an Enterprise Service Bus
Answer: J
NEW QUESTION # 19
CS modules is for
- A. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- B. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- C. Reusable Core Services with public entities, actions, and blocks.
- D. 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.
- E. 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.
Answer: C
NEW QUESTION # 20
What is NOT a best practice for Mobile Application Architecture: Local Storage?
- A. Sync on every screen or online event
- B. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
- C. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
Answer: A
Explanation:
Example: if you are accessing Purchasing data, sync the summary data on Session start. On selecting the Purchasing item, sync the details of the Purchasing item such as photos or price, a
NEW QUESTION # 21
What is NOT a best practice for Mobile Application Architecture: transactions & granularity?
- A. 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.
- B. 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
Answer: B
NEW QUESTION # 22
Which of the following Data elements can we find in a Foundation layer Module?
- A. Non-core Entities
- B. CRUD actions for Entities
- C. Core Entities (exposed as read-only)
- D. Entities to save UI states
Answer: A
NEW QUESTION # 23
Which of the below are not recommendations for Architecture Validations
- A. No core entities in Foundational Modules
- B. No business logic in the Foundational Modules
- C. No screens in the End User Layer
- D. All public entities in Core Modules should be set to Read-only
- E. No front-end screens in Core Modules
Answer: C
NEW QUESTION # 24
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Do not use local storage(mobile device), instead try to use central storage(server side)
- B. Have a local storage inside the CS Module instead of M_CS Module
- C. Use a centralized local storage for all mobile applications to ensure maintainability
- D. Map server side static entities into local entities
Answer: D
NEW QUESTION # 25
In which Architecture Canvas layer do you expect to have a higher reusability rate?
- A. End-User layer
- B. Foundation layer
- C. Core layer
Answer: B
NEW QUESTION # 26
Regarding Validation Rules for application composition, which of the following sentences is correct?
- A. If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.
- B. Common modules and services should be isolated in a separate app that can be referenced by other apps.
- C. Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.
- D. Applications in the Foundation layer can reference Applications in the End-user layer.
Answer: B
NEW QUESTION # 27
......
Architecture-Specialist-11 Premium PDF & Test Engine Files with 85 Questions & Answers: https://exam-labs.itpassleader.com/OutSystems/Architecture-Specialist-11-dumps-pass-exam.html