OutSystems Architecture-Specialist-11 Study Guide Archives Updated on Sep 03, 2024
Download Architecture-Specialist-11 Mock Test Study Material
NEW QUESTION # 23
_Sync module is for
- A. Reusable Core Services with public entities, actions, and blocks.
- B. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- C. 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.
- D. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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 # 24
_CW 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. Reusable Core Services with public entities, actions, and blocks.
- C. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- D. Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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: D
NEW QUESTION # 25
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?
- A. Intranet
- B. Independent Apps
- C. Portal
Answer: C
NEW QUESTION # 26
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Map server side static entities into local entities
- B. Do not use local storage(mobile device), instead try to use central storage(server side)
- C. Have a local storage inside the CS Module instead of M_CS Module
- D. Use a centralized local storage for all mobile applications to ensure maintainability
Answer: A
NEW QUESTION # 27
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.
Answer: A
NEW QUESTION # 28
What is Application Composition Process?
- A. Process to package modules into apps
- B. Answer is the above.
Answer: A
NEW QUESTION # 29
Which of the below is NOT a reason for Validating a Modules' Architecture?
- A. Optimizes lifecycle independence
- B. Promotes abstraction of reusable services
- C. Avoid poor service abstraction
- D. Minimizes impact of changes
- E. Promotes microservices
- F. Prevent slow deployments, inflexible legacy systems
- G. Stop unmanageable dependencies
Answer: E
NEW QUESTION # 30
Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?
- A. Store all records no matter if relevant or irrelevant
- B. Denormalize the local storage
- C. Group relevant information
- D. Define only used attributes
Answer: A
NEW QUESTION # 31
What is NOT a best practice for Mobile Application Architecture: Local Storage?
- A. Sync on every screen or online event
- B. Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
- C. Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
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 # 32
Which of the below is not part of the Architecture Validation Rules?
- A. Layer Applications Correctly
- B. Don't Mix Owners
- C. Layer Modules Correctly
- D. Layer Entities Correctly
- E. Don't Mix Sponsers : Split the Apps based on the Lines of Business
Answer: D
NEW QUESTION # 33
Consider the common style guide scenarios presented in this course. Which of the following statements is true?
- A. Build-your-own Style Guide should be used when the changes in the theme are not extensive.
- B. The "clone a built-in Style Guide" should be used when you want to extend an existing theme.
- C. The "specialize a built-in Style Guide" scenario should be used when the changes to the base theme are not extensive.
Answer: C
NEW QUESTION # 34
In the Architecture Canvas, where should the API module sit in?
- A. End-User Layer
- B. Core Layer
- C. Foundation Layer
Answer: B
NEW QUESTION # 35
In OutSystems, a Foundation Application can NOT contain ...
- A. Core Modules and Foundation Modules.
- B. End-User and Foundation Modules.
- C. End-user and Core Modules.
Answer: C
NEW QUESTION # 36
What is the common naming convention for a mobile version of a CS module?
- A. m_CS
- B. m_cs
- C. _CS
- D. M_CS
- E. mobile_CS
Answer: A
NEW QUESTION # 37
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. ... 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
- C. ... 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
- D. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- E. 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
- F. ... 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
- G. ... 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)
- H. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. 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)
- 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.
Answer: C
NEW QUESTION # 38
_Eng 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. Reusable Core Services with public entities, actions, and blocks.
- C. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.
- D. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- 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: E
NEW QUESTION # 39
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?
- A. Synchronize on every screen or online event for better granularity
No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems. - B. Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.
- C. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
Answer: A
NEW QUESTION # 40
Which is not a reason you should use Architecture Canvas?
- A. Promotes segregation and loose coupling of services
- B. Optimizes lifecycle independence
- C. Promotes abstraction of reusable services
- D. Minimizes impact of changes
Answer: A
NEW QUESTION # 41
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern
- 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. ... 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 - C. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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. . 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. ... 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)
- H. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. ... 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.
- J. 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)
Answer: J
NEW QUESTION # 42
Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.
- A. Don't join concepts with different lifecycles
- B. N/A
- C. Isolate reusable logic from Integration logic
- D. Apply known design patterns
- E. Join conceptually-related concepts
Answer: B
NEW QUESTION # 43
Which of the below is NOT a disadvantage of having a fragmented system or microservices?
- A. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
- B. Security : need to manage credentials and access management
- C. All of the above
- D. Limited data mashup in memory and limited to APIs
- E. Monitoring & Logging : for effective monitoring & logging, requires centralized service
- F. Inter-process communication : network latency and hiccups
- G. Multiple transactions committed independently
- H. Fault tolerance : communication errors, service consistency
Answer: C
NEW QUESTION # 44
Which of the below matches the most to Core Module Pattern - Core Entity 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.
- B. 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
- C. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- D. 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
- 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. ... 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. ... 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- J. 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)
Answer: I
NEW QUESTION # 45
Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?
- A. Information Architecture
- B. Architecture Canvas Modules
- C. Integration Technology
- D. User Experience Expectations
- E. User Stories, Personas and Roles
Answer: B
NEW QUESTION # 46
......
Architecture-Specialist-11 Questions Prepare with Learning Information: https://pass4sure.test4cram.com/Architecture-Specialist-11_real-exam-dumps.html