Architecture-Specialist-11 試験問題を無料オンラインアクセス

What does NOT happen due to a lack of architecture concerns?

• A.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
• 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.Unmanageable dependencies : System not isolated from each other. Updating or replacing a system has a cascade/snowball effect on other systems
• D.Tech Debt : AI Mentor will raise architectural tech debt such as cyclic dependency and side to side dependency

Considering Discovery, which of the following sentences is FALSE?

• A.Discovery only validates architecture rules at the module level.
• B.Discovery automatically assigns a module to an Architecture Canvas layer, following the module's naming convention.
• C.Discovery allows you to determine for every module, which elements are being consumed by other modules.
• D.Discovery cannot categorise modules to domains

Which of the below is NOT a suitable advice for designing a Parallel mobile local storage?

• A.Allow table dependency : Normalize tables to promote parallel data fetch
• B.Avoid generic tables : Contains too much data, not all are relevant
• C.Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady

_Sync module is for

• A.Reusable Core Services with public entities, actions, and blocks.
• 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.Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
• 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.

In the Architecture Canvas, where should the API module sit in?

• A.End-User Layer
• B.Core Layer
• C.Foundation Layer