QUESTION: 29

Which of the below matches the most to Core Module Pattern - Core Entity Pattern...

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

Answer(s): D

Reveal Solution Next Question

QUESTION: 30

Which of the below is not a best practice for mobile security:authentication?

Store password in local storage
Encrypt (only) sensitive data
Authentication : Use google or facebook for online authentication or fingerprint or pin for offline authentication

Answer(s): A

Reveal Solution Next Question

QUESTION: 31

Which are NOT part of the major concepts that needs to be investigated in the Disclose phase in Architecture Design Process?

User Experience Expectations
Integration Technology
User Stories, Personas and Roles
Architecture Canvas Modules
Information Architecture

Answer(s): D

Reveal Solution Next Question

QUESTION: 32

Which of the below is NOT a disadvantage of having a fragmented system or microservices?

All of the above
Monitoring & Logging : for effective monitoring & logging, requires centralized service
Inter-process communication : network latency and hiccups
Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
Security : need to manage credentials and access management
Limited data mashup in memory and limited to APIs
Multiple transactions committed independently
Fault tolerance : communication errors, service consistency

Answer(s): A

Reveal Solution Next Question

Free Architecture-Specialist-11 Exam Braindumps (page: 8)

QUESTION: 29

QUESTION: 30

QUESTION: 31

QUESTION: 32