Top OutSystems Architecture-Specialist-11 Courses Online - Updated [Jan-2024]
Architecture-Specialist-11 Practice Dumps - Verified By GuideTorrent Updated 85 Questions
NEW QUESTION # 50
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern
- A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- D. ... 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
- E. ... 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.
- F. ... 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
- G. 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
- H. ... 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 - I. ... 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)
- 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 # 51
Themes and Layouts are an important element of an application. In which of the following would you define these elements?
- A. MyApp_Th Module, in the End-User layer
- B. MyApp_BL, in the Foundation Layer.
- C. MyApp_MTh, in the Foundation layer.
- D. MyApp_CS Module, in the Foundation layer
Answer: A
NEW QUESTION # 52
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 # 53
Which of the below are not recommendations for Architecture Validations
- A. No screens in the End User Layer
- B. All public entities in Core Modules should be set to Read-only
- C. No front-end screens in Core Modules
- D. No core entities in Foundational Modules
- E. No business logic in the Foundational Modules
Answer: A
NEW QUESTION # 54
Which of the below is NOT a reason why application Architecture is important when building quality software solutions?
- A. Facilitate Change : When something comes up that requires you to veer from the origina design or path, architecture of your system can show you exactly what needs to change and help with communication and planning.
- B. Supports Planning : Helps the team anticipate and build solutions
- C. Drives Consensus : Helps create common ground with the team
- D. Manages Complexity : Helps reduce emerging complexity by focusing on relevant properties and omitting irrelevant details, thus leading to simpler representation
- E. Helps Communication : Helps you to get buy in from the business and to communicate overall plan to them
- F. Reduces Risk : Architecture is a cost effective way to mitigate substantial risks and ensure ^ success
- G. Reduces Costs : Architecture benefits are not only technical, but affect how you operate
Answer: E
NEW QUESTION # 55
Regarding Validation Rules for application composition, which of the following sentences is correct?
- A. Owners of the Application should not be mixed, but mixing Sponsors has no direct impact on the release.
- B. Common modules and services should be isolated in a separate app that can be referenced by other apps.
- C. If you follow all the rules for validating modules, your application composition will be sound, and easy to maintain and deploy.
- D. Applications in the Foundation layer can reference Applications in the End-user layer.
Answer: B
NEW QUESTION # 56
In the Architecture Canvas, where should the API module sit in?
- A. End-User Layer
- B. Foundation Layer
- C. Core Layer
Answer: C
NEW QUESTION # 57
Which of the following Data elements can we find in a Foundation layer Module?
- A. Core Entities (exposed as read-only)
- B. Entities to save UI states
- C. Non-core Entities
- D. CRUD actions for Entities
Answer: C
NEW QUESTION # 58
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- C. ... 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
- D. ... 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.
- E. ... 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
- F. 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
- 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. 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)
- I. ... 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
- J. 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
Answer: I
NEW QUESTION # 59
Which of the below matches the most to Library Module Pattern - Extension Pattern...
- A. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- B. ... 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.
- 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. 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
- 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. Entity is not in Outsystems but in an external ERP system. IS just makes remote call to v 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. Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- H. 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
- I. ... 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)
- J. ... 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
Answer: J
NEW QUESTION # 60
Which of the below is NOT a disadvantage of having a fragmented system or microservices?
- A. Security : need to manage credentials and access management
- B. Limited data mashup in memory and limited to APIs
- C. Inter-process communication : network latency and hiccups
- D. Monitoring & Logging : for effective monitoring & logging, requires centralized service
- E. All of the above
- F. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
- G. Multiple transactions committed independently
- H. Fault tolerance : communication errors, service consistency
Answer: E
NEW QUESTION # 61
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 # 62
Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?
- A. User Experience Expectations
- B. Integration Technology
- C. Architecture Canvas Modules
- D. Information Architecture
- E. User Stories, Personas and Roles
Answer: C
NEW QUESTION # 63
Which is not a reason you should use Architecture Canvas?
- A. Promotes abstraction of reusable services
- B. Optimizes lifecycle independence
- C. Minimizes impact of changes
- D. Promotes segregation and loose coupling of services
Answer: D
NEW QUESTION # 64
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. Group relevant information
- C. Define only used attributes
- D. Denormalize the local storage
Answer: A
NEW QUESTION # 65
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. Independent Apps
- B. Portal
- C. Intranet
Answer: B
NEW QUESTION # 66
"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?
- A. Include the Common flow and Menu artifacts
- B. CSS should only be placed in the mobile theme module
- C. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
- D. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
- E. Blocks grouped in functional modules with independent life cycles
Answer: D
NEW QUESTION # 67
......
New (2024) OutSystems Architecture-Specialist-11 Exam Dumps: https://www.guidetorrent.com/Architecture-Specialist-11-pdf-free-download.html
Updated Architecture-Specialist-11 Exam Dumps - PDF Questions and Testing Engine: https://drive.google.com/open?id=15ulBgzAhNNhy_5aVLXeSTjTtpqrvU89x