[2024年05月26日] Architecture-Specialist-11のPDF問題とテストエンジンには85問があります
更新された試験エンジンはArchitecture-Specialist-11試験無料お試しサンプル365日更新されます
質問 # 20
In OutSystems, a Core Application can contain ...
- A. End-User, Core, and Foundation Modules.
- B. End-User and Core Modules.
- C. Only Foundation Modules.
- D. Foundation and Core Modules
正解：D
質問 # 21
Considering Discovery, which of the following sentences is FALSE?
- A. Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.
- B. Discovery only validates architecture rules at the module level.
- C. Discovery cannot categorise modules to domains
- D. Discovery allows you to determine for every module, which elements are being consumed by other modules.
正解：B
質問 # 22
What is a best practice for Mobile Application Architecture: Local Storage?
- A. Use a centralized local storage for all mobile applications to ensure maintainability
- B. Have a local storage inside the CS Module instead of M_CS Module
- C. Do not use local storage(mobile device), instead try to use central storage(server side)
- D. Map server side static entities into local entities
正解：D
質問 # 23
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Ensure it belongs to the correct layer
- B. Enforce the reference architecture
- C. Normalize known patterns
- D. Reveal nature of each module
正解：A
質問 # 24
Which of the below is NOT a Synchronization Best Practice for mobile application?
- A. 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
- B. Do not use Entity Bulk Operation to ensure small lightweight updates
- C. Sync only when strictly required
E Don't sync on every screen or online event - D. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity
- E. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction - F. Only synchronize relevant data
正解：C
質問 # 25
Which of the following is a benefit of having good architecture?
- A. Unmanageable dependencies
- B. Slow-moving legacy systems
- C. Poor service abstraction
- D. Manages complexity
正解：D
質問 # 26
Which of the below is not part of the Architecture Validation Rules?
- A. Layer Applications Correctly
- B. Layer Modules Correctly
- C. Layer Entities Correctly
- D. Don't Mix Sponsers : Split the Apps based on the Lines of Business
- E. Don't Mix Owners
正解：C
質問 # 27
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... 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.
- B. ... 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
- C. 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
- 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. ... 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
- 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. ... 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. ... 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. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
正解：H
質問 # 28
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
- 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. ... 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.
- C. ... 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.
- D. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
- E. 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
- F. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- G. 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
- 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 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. ... 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
正解：A
質問 # 29
Consider the following Module names and the suggested naming conventions for Modules. Which of these is a mobile Module?
- A. Pricing_MBL
- B. Customer_CW
- C. Mobile_API
- D. Service_CS
正解：A
質問 # 30
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
正解：B
質問 # 31
Which of the below are not recommendations for Architecture Validations
- A. No front-end screens in Core Modules
- B. No business logic in the Foundational Modules
- C. No screens in the End User Layer
- D. No core entities in Foundational Modules
- E. All public entities in Core Modules should be set to Read-only
正解：C
質問 # 32
The Architecture Canvas is a ...
- A. framework to support Architecture Design Process in Outsystems
- B. framework to support application architecture design in Outsystems
- C. framework to support Architecture Conventions for Modules in Outsystems
正解：B
質問 # 33
What is the common naming convention for a mobile version of a CS module?
- A. M_CS
- B. m_CS
- C. mobile_CS
- D. m_cs
- E. _CS
正解：B
質問 # 34
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. Allow table dependency : Normalize tables to promote parallel data fetch
- C. Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady
正解：B
質問 # 35
Which of the below is NOT part of the three step process of Architecture Design Process?
- A. Shape
- B. Disclose
- C. Organize
- D. Assemble
正解：A
質問 # 36
Which of the following recommendations should be applied to the Core layer?
- A. Core modules should not have Core Entities.
- B. Core modules should have Front-end Screens for testing purposes.
- C. Core modules should not have business logic.
- D. Core modules should have public Read-only Entities.
正解：D
質問 # 37
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?
- A. It optimizes lifecycle independence.
- B. It identifies possible performance bottlenecks.
- C. It minimizes the impact of changes.
- D. It promotes a correct abstraction of reusable services.
正解：B
質問 # 38
......
試験合格保証Architecture-Specialist-11試験には正確な問題解答付き：https://jp.fast2test.com/Architecture-Specialist-11-premium-file.html