[Mar-2024] Get 100% Real Architecture-Specialist-11 Exam Questions, Accurate & Verified ActualCollection Dumps in the Real Exam! [Q17-Q39]

Rate this post

[Mar-2024] Get 100% Real Architecture-Specialist-11 Exam Questions, Accurate & Verified ActualCollection Dumps in the Real Exam!

Pass Your Architecture Specialization Exams Fast. All Top Architecture-Specialist-11 Exam Questions Are Covered.

QUESTION 17
Which of the below matches the most to Core Module Pattern – ECS Lazy Load variation

… 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)

… 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 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

… Entity is exposed as read-only and API is available to centralize business logic for entity creation/update

… 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

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 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

… is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.

… a wrapper used to contain the logic, actions and data that will expose code that is inside of i external library or to inspect external database and import the data structures so they can be used as entities inside of OS

QUESTION 18
Foundation may have non-business services and business services in them

TRUE

FALSE

QUESTION 19
“Splitting UI elements per functionality” is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?

Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.

Include the Common flow and Menu artifacts

Put CSS in blocks or screens. Allows better performance and seamless screen transitions

Blocks grouped in functional modules with independent life cycles

CSS should only be placed in the mobile theme module

QUESTION 20
Themes and Layouts are an important element of an application. In which of the following would you define these elements?

MyApp_CS Module, in the Foundation layer

MyApp_BL, in the Foundation Layer.

MyApp_Th Module, in the End-User layer

MyApp_MTh, in the Foundation layer.

QUESTION 21
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.

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

Allow table dependency : Normalize tables to promote parallel data fetch

Use Fetch Data : Avoid cascading aggregates in Onlnitialize and OnReady

Avoid generic tables : Contains too much data, not all are relevant

QUESTION 23
Which of the following is NOT a benefit of having well-defined application architecture?

Poor service abstraction

Reduces costs

Reduces risk

Supports planning

QUESTION 24
Which of the below is NOT a weak dependency as of OS11?

Screens

Static Entities

Server Actions

Database Entities

Service Actions

Local Storage Entities

Structures

QUESTION 25
Which of the below is not part of the Architecture Validation Rules?

Layer Applications Correctly

Don’t Mix Sponsers : Split the Apps based on the Lines of Business

Layer Entities Correctly

Layer Modules Correctly

Don’t Mix Owners

QUESTION 26
Elements such as the menu and login can be shared across different apps. In the menu and login are defined inside the theme. Which use case is this?

Portal

Intranet

Independent Apps

QUESTION 27
OAPI is different compared to API. What is inside an OAPI?

Service Action

REST API

QUESTION 28
Which of the following Data elements can we find in a End-User layer Module?

Non-core Entities

Entities to save UI states

Core Entities (exposed as read-only)

CRUD actions for Entities

QUESTION 29
Consider the common style guide scenarios presented in this course. Which of the following statements is true?

The “specialize a built-in Style Guide” scenario should be used when the changes to the base theme are not extensive.

The “clone a built-in Style Guide” should be used when you want to extend an existing theme.

Build-your-own Style Guide should be used when the changes in the theme are not extensive.

QUESTION 30
Which of the below is NOT a reason for adopting Naming Conventions for Modules

Reveal nature of each module

Ensure it belongs to the correct layer

Enforce the reference architecture

Normalize known patterns

QUESTION 31
What is the common naming convention for a mobile version of a CS module?

M_CS

_CS

mobile_CS

m_cs

m_CS

QUESTION 32
What is NOT a best practice for Mobile Application Architecture: transactions & granularity?

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

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.

QUESTION 33
Which of the below matches the most to Library Module Pattern – Connector Pattern…

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)

… 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

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

… 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

… 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 n 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

… 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 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

QUESTION 34
What is done in the Organize part of the Architecture Design Process?

Concepts are disclosed to the Architecture team

Concepts are assembled into Modules

Concepts are added to the layers of the Architecture Canvas

QUESTION 35
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

QUESTION 36
The Architecture Design Process has three steps. Which of the options below is NOT one of those steps?

Organize

Plan

Assemble

Disclose

QUESTION 37
ISO/IEC 25010:2011 adds two more aspect to ISO/IEC 9126:1991. Which of the below is not part of it?

Compatibility : Compatibility was also added as a way to ensure that a piece of software can work together with other systems

Security : Security ensure software solutions can protect information and data

Integration : Integration to allow data exchange with other software

QUESTION 38
Which of the below are not recommendations for Architecture Validations

All public entities in Core Modules should be set to Read-only

No business logic in the Foundational Modules

No core entities in Foundational Modules

No screens in the End User Layer

No front-end screens in Core Modules

QUESTION 39
Which is not a reason you should use Architecture Canvas?

Promotes segregation and loose coupling of services

Optimizes lifecycle independence

Promotes abstraction of reusable services

Minimizes impact of changes

Penetration testers simulate Architecture-Specialist-11 exam: https://www.actualcollection.com/Architecture-Specialist-11-exam-questions.html

Leave a comment Cancel reply