Free Architecture Specialist (OutSystems 11) Exam Architecture-Specialist-11 Exam Practice Test

In OutSystems, a Core Application can contain ...

• End-User, Core, and Foundation Modules.
• Foundation and Core Modules
• Only Foundation Modules.
• End-User and Core Modules.

_Th module is for

• 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).
• technical wrapper to consume and normalize an external service.
• Theme, look & feel elements, menu, etc.
• Generic Library module.
• Reusable UI Patterns for layout and display only - no Business logic.

Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?

• Enforce the reference architecture.
• Avoid error codes.
• Normalize patterns.
• Reveal the nature of each Module.

What is NOT a best practice for Mobile Application Architecture: Local Storage?

• Adopt the correct sync frequency: Either at process start and online or at process/transaction end and online
• Sync on every screen or online event
• Sync data required per use case: Sync summary data on Session start. On data selection, sync p its details.
• Example: if you are accessing Purchasing data, sync the summary data on Session start. On selecting the Purchasing item, sync the details of the Purchasing item such as photos or price, a

_Eng module is for

• Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, compositio or to have its own lifecycle.
• 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.
• 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.
• Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
• Reusable Core Services with public entities, actions, and blocks.

Which of the following options denotes the advantages of defining a Style Guide up front?

• Security and scalability.
• Speed up the development phase.
• Improve performance and maintainability.
• Allows apps and the Style Guide to be deployed to Production.

SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?

• All of the above are true
• SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks
• SSL Pinning does not mean hardcoding the public key into the code.
• Works on the client side and adds verification of the server certificate against hashes of public keys, which are pre-bundled with the mobile app

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

Which of the below matches the most to Core Module Pattern - Base ECS Pattern...A a wrapper used to contain the logic, actions and data that will expose code that is inside ofexternal library or to inspect external database and import the data structures so they can be used as entities inside of OSB caches only summary data that is frequently lister, joined or searched. Full detail for a singleentry 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 CSD is a pattern with two modules, a connector module that can be used to encapsulate an externalAPI with the input/output structures and a wrapper module to expose the normalized API to the consumers.E is needed if data is coming from MULTIPLE external systems. IS will decide which driver to usedepending on the data.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)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 systemH Entity is not in Outsystems but in an external ERP system. IS just makes remote call to externalsystem/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 casesI 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 frontJ Entity is exposed as read-only and API is available to centralize business logic for entitycreation/update

Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...

• 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 exposed as read-only and API is available to centralize business logic for entity creation/update
• C 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
• 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
• E caches only summary data that is frequently lister, joined or searched. Full detail for a O 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)
• 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 tries to fetch data from local cache entity, if not there, get single entry from the external v
• 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 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.
• 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 is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use
• depending on the data.