Architecture Specialist 11 Dumps Guarantee You Pass Architecture Specialist 11 Exam Easily

Category:

Comments:

0 Comments

Post Date:

December 4, 2023

As new threats and vulnerabilities emerge, the Architecture Specialist 11 exam is updated to reflect the latest trends in Architecture Specialization. By using Architecture Specialist 11 exam dumps questions, you can ensure that you're staying up-to-date with the latest exam content and are fully prepared to address new challenges in Architecture Specialist (OutSystems 11). OutSystems Architecture Specialist 11 exam dumps questions can help you optimize your preparation and ensure that you're fully prepared for the exam. Practice free OutSystems Architecture Specialist 11 exam dumps questions below.

Page 1 of 3

1. Which of the below are FALSE about UI framework?

Patterns - are blocks that provide common and reusable U

Chat message, date picker and carousel are a few examples. Contains reusable UI components.

All of the above are true

Theme - for the look and feel of your applications, which includes screen layouts, global stylesheet and grid definitions. Contains CSS styles and classes.

Templates - Defines the structure of the application modules. Templates contains screen p definitions and basic set of functionalities, including authentication. Contains common layouts, menu, login and reference to the theme.

2. There are 3 common scenarios for Sharing a Style Guide.

Which of the below is not part of th scenario.

Intranet (Single Sign On): Own Menu, Common Login Flow. Menu is defined in the Custom Template, but Login is defined in the Custom Theme. Application reference the Custom Them which picks up the Login.

Enterprise Apps: Common Menu, Common Login Flow. Menu is defined in the Custom Theme, but Login is defined in the Custom Template.

Independent Apps: Own Menu, Own Login Flow. Login and Menu is defined in the Custom Template. Applications reference to its own Application Theme thus do not use the Login and Menu in the Custom Template.

Portal: Common Menu, Common Login Flow. Login and Menu is defined in the Custom Them Application Theme reference the Custom Theme thus have a shared menu and login flow.

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

4. Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern

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

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

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

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

Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration AP

Con: Less impact on source system

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

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

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

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)

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

5. OAPI is different compared to API.

What is inside an OAPI?

Service Action

REST API

6. Concepts are assembled into Modules in the Assembl are not principles in the Assemble step.

Don't join concepts with different lifecycles

Apply known design patterns

N/A

Join conceptually-related concepts

Isolate reusable logic from Integration logic

7. _API module is for

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 AP

Reusable Core Services with public entities, actions, and blocks.

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.

8. "Spaghetti Architecture" is also known as 'tightly coupled architecture' or 'brittle architecture'.

Which is NOT a reason why is "Spaghetti Architecture" bad?

One small change in a component cause a series of cascading effects on other components

Hinder future changes as they become less flexible and difficult to manage

Any changes is maintainable and easy to deploy

9. CS modules is for

Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition 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.

Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the AP

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.

Reusable Core Services with public entities, actions, and blocks.

10. _Lib module is for

have several integration services with different systems, performing the same type of O 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

Reusable Core Services with public entities, actions, and blocks.

Theme, look & feel elements, menu, etc.

Generic Library module

Reusable UI Patterns for layout and display only - no Business logic.

Page 2 of 3

11. Which of the following is NOT a benefit of having well-defined application architecture?

Poor service abstraction

Reduces costs

Reduces risk

Supports planning

12. _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 AP

Reusable Core Services with public entities, actions, and blocks.

13. Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation

Same as Base ECS pattern, but have a local replica. Store data to serve as a local cache. Pro: Leverage Entity Use, Simpler Integration AP

Con: Less impact on source system

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

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 O

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

14. Of the options below, which one is a benefit of adopting the Architecture Canvas?

It's an automatic way to find and fix architecture issues.

It's a systematic approach to architecture design

It promotes the business users' collaboration and understanding

It's a faster architecture design

15. In which of the following scenarios should you choose to clone a built-in Style Guide?

When minor customizations to the base theme should be done inside the app theme.

It is not possible to customize a built-in Style Guide, since it is part of OutSystems U

When you want to introduce extensive changes to an existing theme.

When it is not possible to benefit from any existing theme and extensive changes are needed.

16. Which of the below is not part of the Architecture Validation

No Downward References To Foundation Modules

No Side References Between End-User Modules

No Circular References

No Upward References

17. _Pat module is for

Generic Library module.

Reusable UI Patterns for layout and display only - no Business logic.

Theme, look & feel elements, menu, etc.

technical wrapper to consume and normalize an external service.

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

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

19. Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...

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

Con: Less impact on source system

Same as ECS with direct integration, but through an Enterprise Service Bus

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

... tries to fetch data from local cache entity, if not there, get single entry from the external p 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

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

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

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.

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

Page 3 of 3

21. What is the common naming convention for a mobile version of a CS module?

M_CS

_CS

mobile_CS

m_cs

m_CS

22. The Architecture Design Process has three steps.

Which of the options below is NOT one of those steps?

Organize

Plan

Assemble

Disclose

23. What is the Architecture Blueprint?

Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.

Above is the answer

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

Denormalize the local storage

Define only used attributes

Group relevant information

Store all records no matter if relevant or irrelevant

25. Which of the below is NOT a reason for Validating a Modules' Architecture?

Optimizes lifecycle independence

Promotes microservices

Minimizes impact of changes

Promotes abstraction of reusable services

Stop unmanageable dependencies

Prevent slow deployments, inflexible legacy systems

Avoid poor service abstraction

TAGS:

Architecture Specialist 11, Architecture Specialist 11 exam dumps

Notify of

Label

Name*

Email*

Website

Label

Name*

Email*

Website

0 Comments

Oldest

Newest Most Voted

Inline Feedbacks

View all comments

Posts

Online Associate Reactive Developer Dumps Help You Understand Questions Well

If you're interested in pursuing the Reactive Web Developer certification, it's important to understand the exam format and the types...

Get Architecture Specialist 11 Dumps Full Version

Q&As: 83
Versions: PDF and Software Download Now

About Dumpsinfo

Dumpsinfo is a good platform providing the latest exam information and dumps questions for all IT certification exams. You can study all the latest exam dumps questions online.

[email protected]

Mon - Sat 9:00am - 6:00pm