Free Architecture-Specialist-11: Architecture Specialist (OutSystems 11) Exam Questions and Answers

At the start of a project, an architect interviews business owners to learn the main business concepts, the existing systems of record and the expected consumers of the data, before drawing anything on the Canvas. Which step of the Architecture Design Process is being performed?

• AA. Deploy
• BB. Disclose
• CC. Assemble
• DD. Organize

An architect lists these references found in an environment: 1. Orders_Web (End-User) references Customer_CS (Core). 2. Customer_CS (Core) references Pricing_Lib (Foundation). 3. Orders_Web (End-User) references Billing_Web (End-User). 4. Pricing_Lib (Foundation) references Customer_CS (Core). Which references violate the Architecture Canvas rules?

• AA. 1 and 3
• BB. 2 and 3
• CC. 2 and 4
• DD. 3 and 4

A telecom company is building Core services for six business concepts: Subscriber, SubscriberAddress, Invoice, InvoiceLine, Payment and Tariff. Subscriber data is maintained by the customer care team, Invoice, InvoiceLine and Payment change together under the finance team, and Tariff is changed monthly by the product team. Which Core layer design should the architect choose?

• AA. Entities_CS holding the six entities and Logic_CS holding every action that reads or changes them
• BB. Subscriber_CS, Billing_CS and Tariff_CS, each with the entities of one domain and the actions that manipulate them
• CC. Six Core modules, one per entity, each exposing only the actions that manipulate its own entity
• DD. A single Telecom_CS module holding all six entities together with every action that manipulates them

A team places three elements on the Architecture Canvas. The Customer entity has validation rules and is reused by three applications. The SMS connector wraps a third-party gateway API and contains no business logic. The Checkout screens are used only by the Webshop application. Which assignment to layers is correct?

• AA. Customer entity: End-User; SMS connector: Core; Checkout screens: End-User
• BB. Customer entity: Core; SMS connector: Foundation; Checkout screens: End-User
• CC. Customer entity: Core; SMS connector: End-User; Checkout screens: Foundation
• DD. Customer entity: Foundation; SMS connector: Core; Checkout screens: End-User

Several applications must search and display a catalog of about 40,000 items owned by an external ERP. The catalog changes once a night, reads are frequent and include filtering across the whole catalog, and the ERP is unavailable during a weekly maintenance window. The architect wants to abstract the ERP from the End-User modules. Which approach should be used?

• AA. End-User modules that call the ERP REST API directly and store results in their own entities
• BB. A Core service that fetches items from the ERP on first access and caches them locally
• CC. A Foundation connector that calls the ERP on every request and returns the result unchanged
• DD. A Core service that stores a local replica of the catalog and refreshes it with a Timer

An offline-capable mobile app displays customer data read from Customer_CS. Where should the local storage entities that hold the device copy of that data be defined?

• AA. In a Foundation library referenced by every mobile app
• BB. In the mobile app's own End-User module
• CC. In a separate Core module dedicated to offline data
• DD. In Customer_CS alongside the server-side entities

The Checkout application contains Checkout_Web, Checkout_Mobile and Payment_CS. Payment_CS is owned by the Payments team, changes about once a quarter, and is now referenced by three other applications. Every Checkout release forces the Payments team to take part in the deployment plan. How should the modules be regrouped?

• AA. Split Checkout into one application per module so that each module is deployed on its own
• BB. Move Payment_CS to its own Core application, owned by the Payments team
• CC. Keep Payment_CS in Checkout and use LifeTime tags to deploy it separately from the End-User modules
• DD. Move Payment_CS into the application of its most frequent consumer and publish it with that application

A field-service company builds a mobile app for technicians and a web app for dispatchers. Both apps must apply the same job-assignment rules. Where should these rules be implemented?

• AA. In a Foundation Library module that also stores the assignment data
• BB. In client actions of the mobile module, so that the rules run on the device
• CC. In server actions of the mobile module, which the web module references
• DD. In a Core module that both the mobile and the web modules reference

Three End-User modules each implement the same VAT calculation. The VAT rates are stored in an entity that exists in only one of them, and the other two read it through an exposed entity. What is the best refactoring?

• AA. Move the logic and the rates into a Library module referenced by the three modules
• BB. Duplicate the rate entity in each End-User module and synchronize it with a timer
• CC. Keep the logic in the module that owns the rates and let the other two modules reference it
• DD. Extract the logic and the rate entity into a new Core module referenced by the three modules

Customer_CS contains the Customer entity, the actions that validate and update customers, and the business rules for customer status. It contains nothing unrelated to customers. Which design principle does this module show?

• AA. Independent lifecycle
• BB. Low coupling
• CC. High cohesion
• DD. Service abstraction