Architecture-Specialist-11 무료 덤프문제 온라인 액세스

Which is not a reason you should use Architecture Canvas?

• A.Promotes segregation and loose coupling of services
• B.Minimizes impact of changes
• C.Optimizes lifecycle independence
• D.Promotes abstraction of reusable services

"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

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

• A.Group relevant information
• B.Define only used attributes
• C.Denormalize the local storage
• D.Store all records no matter if relevant or irrelevant

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

Which of the below matches the most to Core Module Pattern - ECS with Local Replica Pattern...

• A.... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
• B.... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
• 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.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.... 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
• 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.... 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
• H.... 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)
• 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.
  p 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