Printable & Easy to Use Architecture-Specialist-11 Dumps 100% Same Q&A In Your Real Exam
Architecture-Specialist-11 Practice Test Give You First Time Success with 100% Money Back Guarantee!
NEW QUESTION # 25
Which is not a reason you should use Architecture Canvas?
- A. Promotes abstraction of reusable services
- B. Minimizes impact of changes
- C. Promotes segregation and loose coupling of services
- D. Optimizes lifecycle independence
Answer: C
NEW QUESTION # 26
Themes and Layouts are an important element of an application. In which of the following would you define these elements?
- A. MyApp_MTh, in the Foundation layer.
- B. MyApp_Th Module, in the End-User layer
- C. MyApp_BL, in the Foundation Layer.
- D. MyApp_CS Module, in the Foundation layer
Answer: B
NEW QUESTION # 27
What is Application Composition Process?
- A. Process to package modules into apps
- B. Answer is the above.
Answer: A
NEW QUESTION # 28
Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?
- A. Mobile_API
- B. Service_CS
- C. Pricing_MBL
- D. Customer_CW
Answer: C
NEW QUESTION # 29
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 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. ... 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- G. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- 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. 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
- J. ... 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)
Answer: F
NEW QUESTION # 30
What does NOT happen due to a lack of architecture concerns?
- A. Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
- B. Poor service abstraction : Business concepts not correctly isolated, business rules tend to be spread over different systems and little to no code reuse
- 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. Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency
Answer: D
NEW QUESTION # 31
There are 3 common scenarios for Sharing a Style Guide. Which of the below is not part of th scenario.
- A. Enterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.
- B. Portal : Common Menu, Common Login Flow. Login and Menu is defined in the Custom Them Application Theme reference the Custom Theme thus have a shared menu and login flow.
- C. Independent Apps : Own Menu, Own Login Flow. Login and Menu is defined in the Custom Template. Applications reference to its own Application Theme thus do not use the Login and Menu in the Custom Template.
- D. Intranet (Single Sign On): Own Menu, Common Login Flow. Menu is defined in the Custom Template, but Login is defined in the Custom Theme. Application reference the Custom Them which picks up the Login.
Answer: A
NEW QUESTION # 32
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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. 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
- D. 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)
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- G. ... 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
- 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. ... 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. ... 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)
Answer: I
NEW QUESTION # 33
Which of the following is an Assembling principle?
- A. Join all integrations into a single Module.
- B. Keep concepts with different lifecycles apart.
- C. Isolate all business concepts.
- D. Disclose business concepts and integration needs.
Answer: B
NEW QUESTION # 34
"Spaghetti Architecture" is also known as 'tightly coupled architecture' or 'brittle architecture'. Which is NOT a reason why is "Spaghetti Architecture" bad?
- A. One small change in a component cause a series of cascading effects on other components
- B. Any changes is maintainable and easy to deploy
- C. Hinder future changes as they become less flexible and difficult to manage
Answer: B
NEW QUESTION # 35
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?
- A. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
- 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. 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.
Answer: C
NEW QUESTION # 36
Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?
- A. Avoid generic tables : Contains too much data, not all are relevant
- B. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
- C. Allow table dependency : Normalize tables to promote parallel data fetch
Answer: C
NEW QUESTION # 37
What is the Architecture Blueprint?
- A. Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.
- B. Above is the answer
Answer: A
NEW QUESTION # 38
Which of the following is NOT a benefit of having well-defined application architecture?
- A. Poor service abstraction
- B. Supports planning
- C. Reduces risk
- D. Reduces costs
Answer: A
NEW QUESTION # 39
ISO/IEC 25010:2011 adds two more aspect to ISO/IEC 9126:1991. Which of the below is not part of it?
- A. Compatibility : Compatibility was also added as a way to ensure that a piece of software can work together with other systems
- B. Security : Security ensure software solutions can protect information and data
- C. Integration : Integration to allow data exchange with other software
Answer: C
NEW QUESTION # 40
_BL module is for
- A. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
- B. 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.
- C. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- 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. Reusable Core Services with public entities, actions, and blocks.
Answer: A
NEW QUESTION # 41
Foundation may have non-business services and business services in them
- A. TRUE
- B. FALSE
Answer: B
NEW QUESTION # 42
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...
- A. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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. 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. 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- F. ... 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
- 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. ... tries to fetch data from local cache entity, if not there, get single entry from the external v 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
- I. ... caches only summary data that is frequently lister, joined or searched. Full detail for a O 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 O external library or to inspect external database and import the data structures so they can be used as entities inside of OS
Answer: D
NEW QUESTION # 43
_Pat module is for
- A. Generic Library module.
- B. technical wrapper to consume and normalize an external service.
- C. Theme, look & feel elements, menu, etc.
- D. Reusable UI Patterns for layout and display only - no Business logic.
- E. to have several integration services with different systems, performing the same type of operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).
Answer: D
NEW QUESTION # 44
......
Fully Updated Free Actual OutSystems Architecture-Specialist-11 Exam Questions: https://certkingdom.practicedump.com/Architecture-Specialist-11-practice-dumps.html