I85PREP
⌘ K
Engineer Architecture study materials
Engineer Architecture study resources

Engineer Architecture practice questions

One question at a time. Build your Engineer Architecture understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Architecture Fundamentals and Design Principles

Which architecture principle states that a module should have only one reason to change, so that each module's responsibilities stay narrowly scoped?

  1. Single Responsibility Principle Correct answer.
  2. Open/Closed Principle
  3. Interface Segregation Principle
  4. Liskov Substitution Principle

Explanation

The Single Responsibility Principle assigns a module exactly one reason to change, tying cohesion to the number of actors it serves. It is distinct from the other SOLID principles, which govern extension, substitutability, and interface granularity rather than change drivers.

Question 2Architecture Fundamentals and Design Principles

A team wants new payment providers to be added without editing the checkout service's existing code. Which principle most directly guides this design?

  1. Dependency Inversion Principle
  2. Single Responsibility Principle
  3. Law of Demeter
  4. Open/Closed Principle Correct answer.

Explanation

The Open/Closed Principle states that software entities should be open for extension but closed for modification, which is exactly the goal of adding providers without editing checkout. It is typically achieved through abstractions such as a provider interface with pluggable implementations.

Question 3Architecture Fundamentals and Design Principles

Which quality attribute describes a system's ability to continue operating correctly when one component fails, without a total outage?

  1. Availability Correct answer.
  2. Maintainability
  3. Scalability
  4. Usability

Explanation

Availability measures the proportion of time a system is operational and serving requests, so surviving a component failure without outage is an availability concern. Resilience tactics such as redundancy and failover are used to raise availability.

Question 4Architecture Fundamentals and Design Principles

In layered architecture, what is the primary purpose of enforcing that a presentation layer may call the domain layer but never the reverse?

  1. To reduce coupling and keep domain logic independent of delivery mechanisms Correct answer.
  2. To eliminate the need for a data access layer
  3. To allow the domain layer to render user interface components directly
  4. To guarantee that the presentation layer can be unit tested without mocks

Explanation

Restricting dependencies to point inward keeps domain logic independent of delivery mechanisms, which lowers coupling and lets UI technology change without touching business rules. The reverse dependency would tie core logic to a specific presentation framework.

Question 5Architecture Fundamentals and Design Principles

Which statement best characterizes a microservices architecture compared with a monolithic one?

  1. Services eliminate the need for operational monitoring
  2. Services must all be written in the same programming language
  3. Services are independently deployable and communicate over network boundaries Correct answer.
  4. Services share a single relational schema to simplify transactions

Explanation

Microservices are independently deployable units that communicate across process and network boundaries, which enables autonomous teams and scaling. That distribution also introduces latency, partial failure, and operational complexity that a monolith avoids.

Question 6Architecture Fundamentals and Design Principles

Which diagram type in UML is intended to show the static structure of classes, their attributes, and their relationships?

  1. Activity diagram
  2. State machine diagram
  3. Class diagram Correct answer.
  4. Sequence diagram

Explanation

A class diagram depicts static structure: classifiers, their attributes and operations, and relationships such as association, inheritance, and dependency. Behavioral diagrams like sequence and activity diagrams instead model interactions or flows over time.

Question 7Architecture Fundamentals and Design Principles

Which coupling type is weakest and therefore most desirable between two modules?

  1. Common coupling through a shared global variable
  2. Content coupling, where one module modifies another's internal data
  3. Control coupling, where one module passes a flag that dictates another's logic
  4. Data coupling, where modules exchange only parameters Correct answer.

Explanation

Data coupling is the weakest common form because modules share only the parameters they need, minimizing hidden dependencies. Stronger forms such as content, common, and control coupling make modules harder to change independently.

Question 8Architecture Fundamentals and Design Principles

What does high cohesion within a module indicate?

  1. The module exposes a large number of public methods
  2. The module is deployed as a separate network service
  3. The module depends on many other modules to function
  4. The module's elements are strongly related and serve a single, focused purpose Correct answer.

Explanation

Cohesion measures how strongly related the responsibilities inside a module are, so high cohesion means a focused, single-purpose module. High cohesion usually pairs with low coupling to produce maintainable designs.

Question 9Architecture Fundamentals and Design Principles

An architect must choose between a relational store and a document store for a system whose records have highly variable, evolving nested attributes. Which reasoning best applies?

  1. Choose the relational store because it forbids schema evolution
  2. Choose the document store because it guarantees ACID transactions across many documents
  3. Choose the relational store because normalization always improves query performance
  4. Choose the document store because schema flexibility suits variable nested records Correct answer.

Explanation

Document stores accommodate variable, evolving nested structures without a fixed relational schema, which fits records whose attributes differ and change over time. The trade-off is that cross-document transactional guarantees and complex joins are typically weaker than in a relational system.

Question 10Architecture Fundamentals and Design Principles

A system must remain responsive during traffic spikes by adding stateless application instances behind a load balancer. Which architectural property is being designed for?

  1. Fault tolerance
  2. Interoperability
  3. Horizontal scalability Correct answer.
  4. Portability

Explanation

Adding stateless instances behind a load balancer is horizontal scaling, which increases capacity by adding nodes rather than enlarging one. Keeping instances stateless ensures any node can serve any request, making the scaling model effective.

Question 11Architecture Fundamentals and Design Principles

A service calls a downstream dependency that occasionally times out. Which resilience pattern prevents a failing dependency from exhausting the caller's threads and cascading failure?

  1. Database sharding
  2. Publish-subscribe
  3. Blue-green deployment
  4. Circuit breaker Correct answer.

Explanation

A circuit breaker trips after repeated failures and fails fast, stopping calls to a struggling dependency so the caller's resources are not exhausted. This contains the failure and allows the dependency time to recover before traffic resumes.

Question 12Architecture Fundamentals and Design Principles

A team applies the Dependency Inversion Principle to a service that currently instantiates a concrete database client directly. Which change best realizes the principle?

  1. Move database calls into the presentation layer to centralize access
  2. Have the service construct the database client in every method that needs it
  3. Have the service depend on a repository interface and inject an implementation at runtime Correct answer.
  4. Merge the database client into the service class to reduce the number of files

Explanation

Dependency Inversion has high-level policy depend on abstractions rather than concrete details, so the service should depend on a repository interface with an implementation supplied from outside. This decouples business logic from the specific database client and allows substitution.

Question 13Architecture Fundamentals and Design Principles

Which tactic most directly improves modifiability of a system where a single change frequently requires edits across many modules?

  1. Removing automated tests to speed up edits
  2. Increasing the number of shared mutable global variables
  3. Consolidating all logic into one large module
  4. Reducing coupling by introducing stable interfaces between modules Correct answer.

Explanation

Modifiability improves when a change is localized, and stable interfaces reduce the ripple effects of coupling across modules. Encapsulating variation behind interfaces means callers are insulated from internal changes.

Question 14Architecture Fundamentals and Design Principles

An architect documents an architecture decision to adopt event-driven integration rather than synchronous REST calls between two systems. Which artifact best captures the rationale and consequences of this choice?

  1. A test plan for the REST endpoints
  2. A capacity plan for the message broker
  3. A class diagram of the message payload
  4. An architecture decision record Correct answer.

Explanation

An architecture decision record captures the context, decision, and consequences of a significant architectural choice so future maintainers understand the rationale. It preserves the why, which ordinary design diagrams and plans do not.

Question 15Architecture Fundamentals and Design Principles

A component needs to notify several unrelated subsystems when an order is placed, and new subscribers are expected over time. Which design approach best limits coupling between the publisher and subscribers?

  1. Embedding subscriber logic inside the order component
  2. Publishing an order event to a broker that subscribers consume Correct answer.
  3. Sharing a global flag that subscribers poll periodically
  4. Directly invoking each subsystem's API from the order component

Explanation

Publishing to an event broker inverts the dependency so the order component need not know its subscribers, and new consumers can be added without modifying the publisher. This is the essence of an implicit invocation or publish-subscribe style.

Question 16Architecture Fundamentals and Design Principles

Which trade-off is most characteristic of adopting a microservices architecture?

  1. Gains a single shared database but loses independent scaling
  2. Gains independent deployability but accepts distributed-system complexity Correct answer.
  3. Gains compile-time type safety but loses network communication
  4. Gains simpler in-process transactions but loses team autonomy

Explanation

Microservices trade the simplicity of in-process calls and transactions for independent deployability and scaling, at the cost of network latency, partial failure, and eventual consistency. Architects must weigh these operational burdens against the autonomy gained.

Question 17Architecture Fundamentals and Design Principles

In a pipes-and-filters architecture, what is the primary benefit of keeping filters independent and unaware of each other?

  1. Filters can share mutable state to reduce copying
  2. Filters eliminate the need for a defined data format between stages
  3. Filters can be reordered, reused, and tested in isolation Correct answer.
  4. Filters guarantee real-time latency across the pipeline

Explanation

Pipes-and-filters treats each filter as a transform on a data stream, so independence lets filters be reordered, reused, and tested separately. The cost is that every stage must agree on the data format carried through the pipes.

Question 18Architecture Fundamentals and Design Principles

Which scenario best justifies choosing a monolithic deployment for a new product?

  1. Components require radically different scaling profiles and technology stacks
  2. A small team needs fast iteration and has no independent scaling requirements yet Correct answer.
  3. Regulatory isolation demands that each component run in a separate trust boundary
  4. Several teams must deploy on independent release cadences from day one

Explanation

A monolith suits a small team with a single deployable and no need for independent scaling, because it minimizes operational overhead and speeds early iteration. Distributed architectures add cost that pays off only when autonomy or scaling demands justify it.

Question 19Architecture Fundamentals and Design Principles

Which practice best supports traceability of an architectural design to stakeholder concerns?

  1. Deferring all architectural documentation until after release
  2. Relying on verbal agreements recorded in meeting memory
  3. Maintaining a requirements-to-component traceability matrix with rationale Correct answer.
  4. Documenting only the final deployment diagram

Explanation

A traceability matrix links each stakeholder concern or requirement to the components that satisfy it, exposing gaps and supporting impact analysis. Pairing it with rationale keeps the mapping meaningful rather than a bare list.

Question 20Architecture Fundamentals and Design Principles

A legacy system must expose its data to a new mobile client without changing its internals. Which pattern isolates the client from the legacy interface?

  1. Observer
  2. Singleton
  3. Strategy
  4. Adapter Correct answer.

Explanation

An adapter translates the legacy interface into the one the new client expects, containing legacy quirks behind a stable contract. This lets the client evolve independently while the legacy system remains untouched.

Question 21Architecture Fundamentals and Design Principles

Two candidate designs satisfy the same functional requirements. Design A localizes the impact of an expected change to one module, while Design B spreads it across five. Under the modifiability quality attribute, which conclusion is best supported?

  1. The designs are equivalent because both meet the functional requirements
  2. Design B is preferable because more modules touched implies better modularity
  3. Design B is preferable because spreading change across modules distributes risk
  4. Design A is preferable because change impact is localized, reducing modification cost Correct answer.

Explanation

Modifiability is evaluated by the cost and scope of making anticipated changes, so confining impact to one module is the stronger design. Meeting functional requirements does not differentiate the designs on this quality attribute.

Question 22Architecture Fundamentals and Design Principles

A team proposes using a shared database across microservices to simplify reporting. Which consequence most directly undermines the architecture's independence goal?

  1. Services must be written in different languages
  2. Deployment frequency increases for each service
  3. Reporting queries become slower because data is centralized
  4. Services become coupled to a shared schema, so changes require cross-team coordination Correct answer.

Explanation

A shared schema turns the database into a coupling point, so altering a table forces coordinated changes across service owners and erodes independent deployability. Data ownership per service is the usual remedy, with reporting handled through projections or events.

Question 23Architecture Fundamentals and Design Principles

An architect must decide whether to invest in a tactic that improves availability but worsens performance. Which approach best supports a defensible decision?

  1. Defer the decision until performance problems appear in production
  2. Adopt both tactics fully without measuring their interaction
  3. Select the tactic with the lowest implementation cost regardless of quality impact
  4. Quantify the trade-off against prioritized quality-attribute scenarios and document the rationale Correct answer.

Explanation

Trade-offs are resolved by evaluating each option against prioritized quality-attribute scenarios with measurable responses, then recording the rationale for the choice. This makes the decision defensible and revisitable as priorities shift.

Question 24Architecture Fundamentals and Design Principles

A system uses synchronous request-response calls in a chain of five services. Analysis shows that end-to-end availability is the product of each service's availability. Which conclusion follows?

  1. Availability of individual services is irrelevant when calls are synchronous
  2. Adding more services to the chain increases end-to-end availability
  3. End-to-end availability equals the highest availability among the five services
  4. Chaining calls compounds unavailability, so asynchronous decoupling or redundancy can raise overall availability Correct answer.

Explanation

When a request requires every service in a synchronous chain, the composite availability is the product of the individual availabilities, so it falls below each component. Decoupling with asynchronous messaging or adding redundancy reduces the compounding effect.

Question 25Architecture Fundamentals and Design Principles

In a layered architecture, a developer places business rules in the persistence layer because it is convenient. Which principle is most directly violated?

  1. Law of Demeter
  2. Interface Segregation Principle
  3. Liskov Substitution Principle
  4. Separation of concerns Correct answer.

Explanation

Separation of concerns requires each layer to address its own responsibility, so placing business rules in persistence mixes domain policy with data storage. This blurs layer boundaries and makes both concerns harder to change and test.

Question 26Architecture Fundamentals and Design Principles

In architecture-centric design, which statement best captures the relationship between quality attributes and functional requirements?

  1. Functional requirements determine whether a system can be built, while quality attributes determine how well it satisfies its stakeholders over time. Correct answer.
  2. Functional requirements should be traded off against each other, while quality attributes are fixed and non-negotiable.
  3. Quality attributes and functional requirements are interchangeable, so documenting one implicitly documents the other.
  4. Quality attributes are secondary concerns that should be deferred until after all functional requirements are implemented.

Explanation

Quality attributes are non-functional characteristics such as availability, modifiability, and performance that shape the architectural structures, whereas functional requirements define what the system does. Architecture exists largely because quality attributes cannot be achieved by functional decomposition alone. Treating them as secondary or interchangeable misrepresents why architecture matters.

Question 27Architecture Fundamentals and Design Principles

An architect is defining module boundaries and wants each module to hide the design decisions most likely to change. Which principle is being applied?

  1. Information hiding as described by Parnas Correct answer.
  2. Separation of concerns across deployment tiers
  3. Strict layering with closed layers
  4. Uniform access to all module internals

Explanation

Parnas argued that modules should be decomposed around design decisions likely to change and should encapsulate those decisions behind stable interfaces. This is the essence of information hiding and is a foundation of modifiability. Layering and separation of concerns are related but do not by themselves dictate hiding volatile decisions.

Question 28Architecture Fundamentals and Design Principles

A team is choosing an architectural style for a workflow where each step may be independently reordered, replaced, or run on different hardware. Which style characteristic most directly supports this?

  1. Shared global state that all steps read and write in place
  2. A single deployable unit containing all processing logic
  3. Independent processing components connected through typed data streams Correct answer.
  4. A central orchestrator that hard-codes the sequence of steps

Explanation

Styles built from independent processing components joined by data streams, such as pipes-and-filters, let each step be replaced or relocated without editing its neighbors, because components interact only through the data contract. This supports reordering and hardware distribution. Shared state and hard-coded orchestration instead increase coupling between steps.

Question 29Architecture Fundamentals and Design Principles

During an architecture evaluation, reviewers map each candidate design decision to the quality attribute scenarios it is meant to satisfy. Which outcome does this practice most directly produce?

  1. A traceable rationale linking design decisions to stakeholder-driven quality scenarios Correct answer.
  2. A fixed cost estimate that removes the need for later re-planning
  3. A complete elimination of architectural risk before implementation
  4. A guarantee that the system will meet every performance target

Explanation

Mapping decisions to quality attribute scenarios creates traceability from stakeholder concerns through measurable scenarios to the structures chosen to satisfy them. It makes the reasoning reviewable and exposes decisions that lack a justifying scenario. It cannot guarantee outcomes or eliminate risk, since risk is managed rather than removed.

Question 30Architecture Fundamentals and Design Principles

Two designs satisfy identical functional requirements. Design A places a volatile business rule in one module referenced by three others; Design B duplicates the rule in each of the four modules. Which analysis of expected change cost is most defensible?

  1. Design B is preferable because it removes all coupling between the modules.
  2. Design A is preferable because a single change touches one module, though its three dependents must still be recompiled and retested. Correct answer.
  3. Design B is preferable because duplication always reduces the blast radius of a change.
  4. The two designs are equivalent because both satisfy the same functional requirements.

Explanation

Localizing a volatile rule in one module reduces the number of edits per change, which is the core modifiability benefit, but the dependents that reference it still impose recompilation and regression testing costs. That nuance makes Design A preferable without overstating the benefit. Duplication multiplies the edit points and does not remove coupling.

Question 31Requirements Engineering and Stakeholder Analysis

In requirements engineering, which artifact records the rationale behind a design decision so that future maintainers understand why an alternative was rejected?

  1. A test coverage report
  2. A deployment runbook
  3. An architecture decision record Correct answer.
  4. A burn-down chart

Explanation

An architecture decision record captures the context, the decision taken, and the consequences, including rejected alternatives. This preserves rationale across time and personnel changes, which a burn-down chart, coverage report, or runbook does not attempt to do.

Question 32Requirements Engineering and Stakeholder Analysis

Which stakeholder classification distinguishes people who affect the system from those who are affected by it but hold no influence over its design?

  1. Primary versus secondary stakeholders Correct answer.
  2. Baseline versus current state
  3. Shall versus should statements
  4. Functional versus non-functional requirements

Explanation

Primary stakeholders are directly affected or directly influence the system, while secondary stakeholders are indirectly affected and typically have less influence. The other pairs describe requirement types or document states, not people.

Question 33Requirements Engineering and Stakeholder Analysis

A requirement states: "The system shall respond to any search query within two seconds." Which quality attribute does this requirement primarily constrain?

  1. Performance Correct answer.
  2. Security
  3. Usability
  4. Portability

Explanation

A response-time bound is a performance constraint, expressed as a measurable non-functional requirement. Portability concerns moving between environments, usability concerns ease of use, and security concerns protection of assets.

Question 34Requirements Engineering and Stakeholder Analysis

Why is traceability between requirements and design elements valuable during architecture work?

  1. It automatically resolves conflicting stakeholder goals
  2. It removes the need to prioritize requirements by business value
  3. It guarantees that all requirements are testable without further analysis
  4. It shows which design elements satisfy which requirements and exposes gaps or orphans Correct answer.

Explanation

Traceability links each requirement to design and test artifacts, making coverage gaps and orphaned design elements visible. It does not by itself make requirements testable, replace prioritization, or resolve conflicts among stakeholders.

Question 35Requirements Engineering and Stakeholder Analysis

Which technique gathers requirements by having a facilitator lead a structured session in which stakeholders brainstorm and then consolidate candidate requirements?

  1. Requirements workshop Correct answer.
  2. Regression testing
  3. Formal inspection
  4. Fault tree analysis

Explanation

A requirements workshop is a facilitated, structured group session used to elicit and consolidate requirements from multiple stakeholders. Formal inspection reviews existing artifacts, fault tree analysis examines failure causes, and regression testing verifies unchanged behavior.

Question 36Requirements Engineering and Stakeholder Analysis

What does a requirements baseline represent in a controlled architecture project?

  1. A list of requirements that stakeholders have requested but not yet approved
  2. An agreed, formally reviewed set of requirements that changes only through change control Correct answer.
  3. The first draft produced during elicitation before any review
  4. The set of requirements implemented in the most recent release

Explanation

A baseline is a formally agreed snapshot of requirements placed under configuration and change control. Drafts, unapproved requests, and release contents are distinct states that do not carry the same controlled status.

Question 37Requirements Engineering and Stakeholder Analysis

A stakeholder states that the system must be "user friendly." Which rewrite best converts this into an architecturally actionable requirement?

  1. The system shall have an attractive graphical interface
  2. Users shall find the system easy to learn and pleasant to use
  3. The interface shall follow good design principles throughout
  4. A trained user shall complete the checkout task in under three minutes with no more than one error Correct answer.

Explanation

An actionable requirement specifies a measurable outcome, an actor, and conditions so that it can be verified and drive design. The other options restate subjective qualities without measurable criteria.

Question 38Requirements Engineering and Stakeholder Analysis

Two stakeholders demand mutually exclusive encryption strengths for the same data flow. What is the most appropriate next step in requirements engineering?

  1. Remove both requirements so the conflict disappears from the specification
  2. Document the conflict, analyze trade-offs with both parties, and record the negotiated resolution Correct answer.
  3. Silently adopt the stricter option to avoid further discussion
  4. Defer the decision to the implementation team without recording the conflict

Explanation

Conflicting requirements should be made explicit, analyzed against cost, risk, and stakeholder value, and resolved through negotiation with the parties involved. The resolution and its rationale must then be recorded so the decision is traceable.

Question 39Requirements Engineering and Stakeholder Analysis

An architect needs to understand the sequence of steps a clerk performs and the exceptions that interrupt them. Which elicitation technique is most directly suited to this goal?

  1. A cost-benefit analysis of candidate vendors
  2. Observation combined with contextual inquiry Correct answer.
  3. Review of the existing data dictionary
  4. A survey distributed to all employees

Explanation

Observing work in context reveals actual task sequences and exception handling that interviewees may omit or misreport. Surveys, data dictionaries, and vendor analysis do not capture procedural detail and interruptions directly.

Question 40Requirements Engineering and Stakeholder Analysis

A requirement reads: "If the payment gateway is unavailable, the order service shall queue the transaction and retry for up to ten minutes." Which characteristic does this requirement demonstrate?

  1. It states a business goal without measurable criteria
  2. It leaves the failure handling entirely to the implementer
  3. It describes an internal design pattern rather than required behavior
  4. It specifies a defined response to a specific exceptional condition Correct answer.

Explanation

The statement pairs a triggering condition with a bounded, observable response, making it verifiable and design-relevant. It does not dictate a specific internal pattern and it does not leave failure handling undefined.

Question 41Requirements Engineering and Stakeholder Analysis

Which view of stakeholders is most useful when assessing who must approve a requirements baseline?

  1. A power and interest grid that maps influence against concern Correct answer.
  2. A work breakdown structure of project tasks
  3. A burn-up chart of completed features
  4. A network diagram of system components

Explanation

A power and interest grid helps identify which stakeholders hold approval authority and which need to be kept informed. Work breakdown structures, component diagrams, and burn-up charts describe work, architecture, or progress rather than stakeholder influence.

Question 42Requirements Engineering and Stakeholder Analysis

During validation, reviewers find a requirement that cannot be verified by any feasible test or inspection. What is the most appropriate classification of this defect?

  1. The requirement is out of scope and should be deleted immediately
  2. The requirement is a duplicate and should be merged with another
  3. The requirement is a design constraint and should move to the architecture document
  4. The requirement is not verifiable and must be rewritten with measurable criteria Correct answer.

Explanation

A requirement that cannot be checked against defined criteria fails the verifiability quality attribute and should be restated measurably. Nothing in the scenario indicates duplication, scope problems, or that the item is actually a design constraint.

Question 43Requirements Engineering and Stakeholder Analysis

A team uses user stories with acceptance criteria. What is the primary role of the acceptance criteria in architecture planning?

  1. They replace the need for any non-functional requirements
  2. They specify the internal class structure of the implementation
  3. They record the estimated effort for each story
  4. They define the conditions that must hold for the story to be accepted and guide what the architecture must support Correct answer.

Explanation

Acceptance criteria state the observable conditions for accepting a story and therefore constrain what the architecture must enable. They do not substitute for non-functional requirements, dictate internal class design, or serve as effort estimates.

Question 44Requirements Engineering and Stakeholder Analysis

An architect is prioritizing non-functional requirements. Which approach best supports defensible trade-off decisions among competing quality attributes?

  1. Elicit concrete quality scenarios with stimulus, response, and measure, then rank them by business and risk impact Correct answer.
  2. Adopt the highest value for every quality attribute to avoid missing targets
  3. Defer all quality decisions until performance testing begins
  4. Rank quality attributes alphabetically to ensure consistent treatment

Explanation

Quality scenarios make non-functional requirements concrete and testable, and ranking them by business value and risk yields defensible trade-offs. Maximizing everything is infeasible, arbitrary ordering is indefensible, and deferral delays necessary architectural decisions.

Question 45Requirements Engineering and Stakeholder Analysis

Which situation most clearly indicates scope creep rather than legitimate requirements evolution?

  1. A stakeholder clarifies an ambiguous requirement during a review
  2. A requirement is refined into smaller stories for planning
  3. New features are added repeatedly without change control, schedule adjustment, or stakeholder approval Correct answer.
  4. A defect in a requirement is corrected after validation

Explanation

Scope creep is uncontrolled expansion of scope without corresponding approval, re-planning, or change control. Clarification, correction, and decomposition are normal, controlled refinement activities within requirements engineering.

Question 46Requirements Engineering and Stakeholder Analysis

An architect must select an elicitation approach for a domain where experts are geographically dispersed, highly opinionated, and unlikely to agree in a single meeting. Which combination is most appropriate?

  1. Structured interviews followed by an asynchronous Delphi-style convergence round Correct answer.
  2. Analysis of legacy source code alone
  3. A single unstructured group brainstorm with no follow-up
  4. Passive observation of one expert's daily work only

Explanation

Structured interviews capture individual positions, and a Delphi-style round lets dispersed experts converge anonymously, reducing domination by vocal participants. A single unstructured session, one-person observation, or code-only analysis would miss the breadth of expert input.

Question 47Requirements Engineering and Stakeholder Analysis

A requirements specification describes a system's functional behavior but omits any measurable quality scenarios. What is the most significant architectural consequence?

  1. The system will necessarily fail to compile
  2. The requirements baseline cannot be placed under version control
  3. Architects cannot evaluate whether candidate structures satisfy performance, availability, or security needs Correct answer.
  4. Stakeholder interviews become impossible to conduct

Explanation

Without measurable quality scenarios, architects lack criteria to assess candidate structures against quality attributes, so structural decisions become ungrounded. Compilation, interviewing, and version control are unaffected by the omission.

Question 48Requirements Engineering and Stakeholder Analysis

A stakeholder with high authority but low technical interest requests a specific database product in the requirements. How should the architect handle this input?

  1. Escalate it as a conflict without first clarifying the stakeholder's intent
  2. Reject it because the stakeholder lacks technical interest
  3. Treat it as a constraint to be recorded and assessed for impact, while clarifying whether it is mandatory or preferred Correct answer.
  4. Accept it silently and remove all competing options from consideration

Explanation

A high-authority request should be captured as a candidate constraint and assessed for architectural impact, with its mandatory or preferred status clarified first. Rejecting it, accepting it uncritically, or escalating prematurely all skip necessary analysis.

Question 49Requirements Engineering and Stakeholder Analysis

Which traceability link is most important for demonstrating that a safety-critical requirement has been addressed in the architecture?

  1. A link from the user manual to the training plan
  2. A link from the source repository to the issue tracker
  3. A link from the safety requirement to the architectural elements and verification evidence that satisfy it Correct answer.
  4. A link from the project schedule to the budget forecast

Explanation

For safety-critical requirements, traceability must connect the requirement to the design elements that realize it and to the verification evidence proving satisfaction. The other links concern project management or operational documentation, not requirement satisfaction.

Question 50Requirements Engineering and Stakeholder Analysis

An architect receives a signed-off requirements specification in which every functional requirement is numbered, but quality attributes appear only as adjectives such as "fast", "secure", and "scalable". Which action best addresses this gap in an architecture engagement?

  1. Select the technology stack the team already knows best, because familiar technology removes the need for explicit quality targets
  2. Elicit measurable quality attribute scenarios with the stakeholders and add them to the specification before committing to architectural drivers Correct answer.
  3. Defer all quality concerns to the implementation phase, since functional requirements are the only ones the architecture must satisfy
  4. Record the adjectives verbatim in the architecture document so that later testing can interpret them at its own discretion

Explanation

Quality attributes stated as adjectives cannot be tested or traded off, so the architect must convert them into scenarios with stimulus, response, and measurable response criteria agreed with stakeholders. Those scenarios then become the architectural drivers that justify structural decisions and later verification.