[2024年更新]Architecture-Specialist-11回答無料デモは最適で最高のリアルな試験合格させます
Architecture-Specialist-11[2024年08月最新推薦]試験問題はあなたをパスさせる
質問 # 31
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. 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)
- C. ... 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
- 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. Same as ECS with direct integration, but through an Enterprise Service Bus
- G. ... 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
- 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. ... 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.
- J. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
正解：F
質問 # 32
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.
正解：C
質問 # 33
_Lib module is for
- A. Technical wrapper to consume and normalize an external service
- B. Reusable UI Patterns for layout and display only - no Business logic.
- C. Theme, look & feel elements, menu, etc.
- D. Generic Library module
- E. have several integration services with different systems, performing the same type of O operation (e.g. printers) you can create several drivers exposing the same API, with specialized implementations (like the transparency services pattern).
- F. Reusable Core Services with public entities, actions, and blocks.
正解：D
質問 # 34
Which of the below is NOT part of the three step process of Architecture Design Process?
- A. Shape
- B. Organize
- C. Disclose
- D. Assemble
正解：A
質問 # 35
Which of the below is NOT a weak dependency as of OS11?
- A. Static Entities
- B. Screens
- C. Service Actions
- D. Structures
- E. Database Entities
- F. Local Storage Entities
- G. Server Actions
正解：G
質問 # 36
_Sync module is for
- A. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- B. 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.
- C. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- D. Reusable Core Services with public entities, actions, and blocks.
- 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.
正解：B
質問 # 37
_API module is for
- A. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- B. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- 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. Reusable Core Services with public entities, actions, and blocks.
- 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.
正解：A
質問 # 38
In the Architecture Canvas, where should the API module sit in?
- A. Foundation Layer
- B. End-User Layer
- C. Core Layer
正解：C
質問 # 39
_IS module is for
- A. 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).
- B. Reusable UI Patterns for layout and display only - no Business logic.
- C. technical wrapper to consume and normalize an external service.
- D. Theme, look & feel elements, menu, etc.
- E. Generic Library module.
正解：C
質問 # 40
Which of the following is a benefit of having good architecture?
- A. Poor service abstraction
- B. Slow-moving legacy systems
- C. Manages complexity
- D. Unmanageable dependencies
正解：C
質問 # 41
_BL 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. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
- C. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- D. Reusable Core Services with public entities, actions, and blocks.
- 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.
正解：B
質問 # 42
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.
正解：A
質問 # 43
CS modules is for
- A. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- B. 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.
- C. Reusable Core Services with public entities, actions, and blocks.
- 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.
正解：C
質問 # 44
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Ensure it belongs to the correct layer
- B. Normalize known patterns
- C. Reveal nature of each module
- D. Enforce the reference architecture
正解：A
質問 # 45
Considering Discovery, which of the following sentences is FALSE?
- A. Discovery allows you to determine for every module, which elements are being consumed by other modules.
- B. Discovery cannot categorise modules to domains
- 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.
正解：D
質問 # 46
Which of the following Data elements can we find in a Foundation layer Module?
- A. Entities to save UI states
- B. Core Entities (exposed as read-only)
- C. Non-core Entities
- D. CRUD actions for Entities
正解：C
質問 # 47
_Pat module is for
- A. Reusable UI Patterns for layout and display only - no Business logic.
- B. technical wrapper to consume and normalize an external service.
- 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. Theme, look & feel elements, menu, etc.
- E. Generic Library module.
正解：A
質問 # 48
What is Application Composition Process?
- A. Process to package modules into apps
- B. Answer is the above.
正解：A
質問 # 49
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 core entities in Foundational Modules
- D. No business logic in the Foundational Modules
- E. No front-end screens in Core Modules
正解：A
質問 # 50
Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?
- A. Avoid error codes.
- B. Reveal the nature of each Module.
- C. Enforce the reference architecture.
- D. Normalize patterns.
正解：A
質問 # 51
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. Integration Technology
- C. Architecture Canvas Modules
- D. User Experience Expectations
- E. User Stories, Personas and Roles
正解：C
質問 # 52
Which of the below is NOT a Synchronization Best Practice for mobile application?
- A. Do not use Entity Bulk Operation to ensure small lightweight updates
- B. Only synchronize delta : Use control timestamps
C Avoid long synchronization in a single transaction - C. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity
- D. Only synchronize relevant data
- E. 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
- F. Sync only when strictly required
E Don't sync on every screen or online event
正解：F
質問 # 53
......
2024年最新のリアル無料OutSystems Architecture-Specialist-11試験問題集問題アンサー：https://www.passtest.jp/OutSystems/Architecture-Specialist-11-shiken.html
OutSystems Architecture-Specialist-11試験良質な問題で回答：https://drive.google.com/open?id=1DGC79SkYjaKo0vq6_17CVB3Ox_6sQWob