[2024] Pass Key features of Architecture-Specialist-11 Course with Updated 85 Questions
Architecture-Specialist-11 Sample Practice Exam Questions 2024 Updated Verified
NEW QUESTION # 17
Which of the below matches the most to Core Module Pattern - ECS Summary Cache only variation
- A. ... 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
- B. ... 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)
- C. ... 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.
- 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. ... 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
- F. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- G. ... 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.
- H. 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
- I. 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
- J. ... Entity is exposed as read-only and API is available to centralize business logic for entity ^ creation/update
Answer: B
NEW QUESTION # 18
What is NOT a best practice for Mobile Application Architecture: Limit server side calls?
- A. Direct calls is bad from Security, Performance and Maintainability standpoint. Direct calls will require javascript Code and javascript Code is harder to maintain.
- B. Synchronize on every screen or online event for better granularity
No direct calls to backend systems. Do call to Outsystems Core Services and Outsystems will handle the interaction with external backend systems. - C. Limit Server side calls to online transactions or Synchronization. Do the bulk of the operations on the Client Side before passing information to the Server Side.
Answer: B
NEW QUESTION # 19
Which of the below matches the most to Core Module Pattern - Base ECS Pattern...
- A. ... 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
- B. ... 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)
- C. 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)
- D. ... 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
- E. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- F. ... 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.
- G. ... 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
- H. 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
- I. 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
- J. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
Answer: F
NEW QUESTION # 20
SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?
- A. SSL Pinning does not mean hardcoding the public key into the code.
- B. All of the above are true
- C. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks
- D. 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
Answer: A
NEW QUESTION # 21
_Lib module is for
- A. Generic Library module
- B. Technical wrapper to consume and normalize an external service
- C. 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).
- D. Reusable Core Services with public entities, actions, and blocks.
- E. Theme, look & feel elements, menu, etc.
- F. Reusable UI Patterns for layout and display only - no Business logic.
Answer: A
NEW QUESTION # 22
What is the common naming convention for a mobile version of a CS module?
- A. m_cs
- B. _CS
- C. mobile_CS
- D. M_CS
- E. m_CS
Answer: E
NEW QUESTION # 23
Adopting a naming convention can have some benefits. Of the sentences below, which one is NOT a benefit of adopting a naming convention?
- A. Normalize patterns.
- B. Avoid error codes.
- C. Reveal the nature of each Module.
- D. Enforce the reference architecture.
Answer: B
NEW QUESTION # 24
Which of the below is NOT a disadvantage of having a fragmented system or microservices?
- A. Monitoring & Logging : for effective monitoring & logging, requires centralized service
- B. Complicated Debugging and troubleshooting : root cause may be deep inside the chain of services
- C. Security : need to manage credentials and access management
- D. Inter-process communication : network latency and hiccups
- E. Fault tolerance : communication errors, service consistency
- F. All of the above
- G. Limited data mashup in memory and limited to APIs
- H. Multiple transactions committed independently
Answer: F
NEW QUESTION # 25
What is the Architecture Blueprint?
- A. Above is the answer
- B. Is the end result of Architecture Design Process. At this point you should add dependencies between the Modules.
Answer: B
NEW QUESTION # 26
Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?
- A. Store all records no matter if relevant or irrelevant
- B. Group relevant information
- C. Define only used attributes
- D. Denormalize the local storage
Answer: A
NEW QUESTION # 27
Which of the below is NOT part of the three step process of Architecture Design Process?
- A. Assemble
- B. Organize
- C. Shape
- D. Disclose
Answer: C
NEW QUESTION # 28
_IS module is for
- A. technical wrapper to consume and normalize an external service.
- B. 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).
- C. Theme, look & feel elements, menu, etc.
- D. Generic Library module.
- E. Reusable UI Patterns for layout and display only - no Business logic.
Answer: A
NEW QUESTION # 29
_Pat module is for
- A. technical wrapper to consume and normalize an external service.
- B. Reusable UI Patterns for layout and display only - no Business logic.
- C. 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).
- D. Theme, look & feel elements, menu, etc.
- E. Generic Library module.
Answer: B
NEW QUESTION # 30
_BL module is for
- A. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
- B. 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.
- C. 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.
- D. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- E. Reusable Core Services with public entities, actions, and blocks.
Answer: A
NEW QUESTION # 31
"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?
- A. CSS should only be placed in the mobile theme module
- B. Put CSS in blocks or screens. Allows better performance and seamless screen transitions
- C. Blocks grouped in functional modules with independent life cycles
- D. Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
- E. Include the Common flow and Menu artifacts
Answer: B
NEW QUESTION # 32
Which of the below is NOT a reason for adopting Naming Conventions for Modules
- A. Ensure it belongs to the correct layer
- B. Enforce the reference architecture
- C. Reveal nature of each module
- D. Normalize known patterns
Answer: A
NEW QUESTION # 33
_Sync module is for
- A. 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.
- B. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.
- C. Isolated Business Logic (Actions) or Core Widgets (blocks), to manage complexity, composition or to have its own lifecycle.
- D. Reusable Core Services with public entities, actions, and blocks.
- E. 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.
Answer: E
NEW QUESTION # 34
_Th module is for
- A. technical wrapper to consume and normalize an external service.
- B. 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).
- C. Generic Library module.
- D. Theme, look & feel elements, menu, etc.
- E. Reusable UI Patterns for layout and display only - no Business logic.
Answer: D
NEW QUESTION # 35
Which is not a reason you should use Architecture Canvas?
- A. Promotes segregation and loose coupling of services
- B. Optimizes lifecycle independence
- C. Minimizes impact of changes
- D. Promotes abstraction of reusable services
Answer: A
NEW QUESTION # 36
Which of the below matches the most to Core Module Pattern - ECS Lazy Load variation
- A. ... 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.
- B. ... 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)
- C. ... 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
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- F. ... 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
- G. ... 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
- H. 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
- I. 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
- J. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
Answer: C
NEW QUESTION # 37
The Architecture Canvas is a multi-layer framework. Which of the following is NOT a benefit of this framework?
- A. It identifies possible performance bottlenecks.
- B. It promotes a correct abstraction of reusable services.
- C. It optimizes lifecycle independence.
- D. It minimizes the impact of changes.
Answer: A
NEW QUESTION # 38
Which of the below matches the most to Core Module Pattern - ECS with Isolated Synchronization Logic Pattern...
- A. ... 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
- B. ... 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.
- C. 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
- 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. ... is needed if data is coming from MULTIPLE external systems. IS will decide which driver to use depending on the data.
- F. ... 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
- G. 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
- H. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
- I. ... 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)
- J. ... 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
Answer: C
NEW QUESTION # 39
In which of the following scenarios should you choose to clone a built-in Style Guide?
- A. When it is not possible to benefit from any existing theme and extensive changes are needed.
- B. When minor customizations to the base theme should be done inside the app theme.
- C. It is not possible to customize a built-in Style Guide, since it is part of OutSystems UI.
- D. When you want to introduce extensive changes to an existing theme.
Answer: D
NEW QUESTION # 40
......
The New Architecture-Specialist-11 2024 Updated Verified Study Guides & Best Courses: https://www.torrentvce.com/Architecture-Specialist-11-valid-vce-collection.html
Exam Study Guide Free Practice Test LAST UPDATED : https://drive.google.com/open?id=1diwCgs9XE8YwyyVscn5G5gC3bsh0qROh