Latest Success Metrics For Actual Architecture-Specialist-11 Exam 2025 Realistic Dumps
Updated Architecture-Specialist-11 Dumps Questions For OutSystems Exam
NEW QUESTION # 26
Which of the below is NOT part of the three step process of Architecture Design Process?
- A. Disclose
- B. Organize
- C. Shape
- D. Assemble
Answer: C
NEW QUESTION # 27
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. 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.
- 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. 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.
Answer: A
NEW QUESTION # 28
In which of the following scenarios should you choose to clone a built-in Style Guide?
- A. When minor customizations to the base theme should be done inside the app theme.
- B. When you want to introduce extensive changes to an existing theme.
- C. When it is not possible to benefit from any existing theme and extensive changes are needed.
- D. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
Answer: B
NEW QUESTION # 29
In OutSystems, a Core Application can contain ...
- A. End-User, Core, and Foundation Modules.
- B. Only Foundation Modules.
- C. End-User and Core Modules.
- D. Foundation and Core Modules
Answer: D
NEW QUESTION # 30
Considering Discovery, which of the following sentences is FALSE?
- A. Discovery cannot categorise modules to domains
- B. Discovery allows you to determine for every module, which elements are being consumed by other modules.
- C. Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.
- D. Discovery only validates architecture rules at the module level.
Answer: D
NEW QUESTION # 31
_IS module is for
- A. Generic Library module.
- B. Reusable UI Patterns for layout and display only - no Business logic.
- C. Theme, look & feel elements, menu, etc.
- D. technical wrapper to consume and normalize an external service.
- E. 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 # 32
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Enforce the reference architecture
- B. Reveal nature of each module
- C. Ensure it belongs to the correct layer
- D. Normalize known patterns
Answer: C
NEW QUESTION # 33
_Th module is for
- A. Generic Library module.
- B. Reusable UI Patterns for layout and display only - no Business logic.
- C. 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).
- D. technical wrapper to consume and normalize an external service.
- E. Theme, look & feel elements, menu, etc.
Answer: E
NEW QUESTION # 34
Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?
- A. Service_CS
- B. Mobile_API
- C. Customer_CW
- D. Pricing_MBL
Answer: D
NEW QUESTION # 35
Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern
- A. ... 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
- B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- C. ... 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)
- 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. . 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. 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)
- 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 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. ... 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 - J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: F
NEW QUESTION # 36
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 # 37
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. Monitoring & Logging : for effective monitoring & logging, requires centralized service
- C. Fault tolerance : communication errors, service consistency
- D. Inter-process communication : network latency and hiccups
- E. All of the above
- F. Limited data mashup in memory and limited to APIs
- G. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
- H. Multiple transactions committed independently
Answer: E
NEW QUESTION # 38
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... 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
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- D. ... 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)
- 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. ... 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.
- G. 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)
- 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 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
- J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: A
NEW QUESTION # 39
Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...
- A. ... 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
- B. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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. ... 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
- 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. 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. Same as ECS with direct integration, but through an Enterprise Service Bus
- H. ... 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.
- I. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- J. ... 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
Answer: G
NEW QUESTION # 40
What is done in the Organize part of the Architecture Design Process?
- A. Concepts are assembled into Modules
- B. Concepts are added to the layers of the Architecture Canvas
- C. Concepts are disclosed to the Architecture team
Answer: B
NEW QUESTION # 41
Which of the below matches the most to Library Module Pattern - Connector Pattern...
- A. ... 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
- 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- D. ... 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)
- 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. 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)
- G. ... tries to fetch data from local cache entity, if not there, get single entry from the external n 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
- 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. 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: I
NEW QUESTION # 42
Which of the following is an Assembling principle?
- A. Isolate all business concepts.
- B. Disclose business concepts and integration needs.
- C. Join all integrations into a single Module.
- D. Keep concepts with different lifecycles apart.
Answer: D
NEW QUESTION # 43
The Architecture Canvas is a ...
- A. framework to support Architecture Conventions for Modules in Outsystems
- B. framework to support application architecture design in Outsystems
- C. framework to support Architecture Design Process in Outsystems
Answer: B
NEW QUESTION # 44
Which of the below is NOT a Synchronization Best Practice for mobile application?
- A. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity
- B. Do not use Entity Bulk Operation to ensure small lightweight updates
- C. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server
- D. Only synchronize relevant data
- E. Sync only when strictly required
E Don't sync on every screen or online event - F. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction
Answer: E
NEW QUESTION # 45
Which of the below matches the most to Library Module Pattern - Extension 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. Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- 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. ... 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. 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 ) 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 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
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
Answer: F
NEW QUESTION # 46
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.
Answer: B
NEW QUESTION # 47
......
Full Architecture-Specialist-11 Practice Test and 85 Unique Questions, Get it Now!: https://www.vceprep.com/Architecture-Specialist-11-latest-vce-prep.html
Best Value Available Preparation Guide for Architecture-Specialist-11 Exam: https://drive.google.com/open?id=13wmq4oCfMo6dhSH1UztwAoRMm03euEpn