An architect is assembling a solution for a customer that has three sites, a small central team, a requirement for each site to keep operating independently during a link failure, and a wish to see the whole estate reported on in one place. Which elements must the assembled solution include? (Choose two.)
A private cloud offers a defined catalogue of environments teams may request. What does the customer give up in exchange for the speed this provides?
Which inputs shape which offering is recommended to a customer? (Choose three.)
A customer is considering expanding a solution that was justified two years ago on a business case they approved. How should the expansion proposal treat that original case?
During discovery, a customer's operations lead says any new system must use the monitoring tooling already in place. Its security lead says all new systems must be monitored through a separate platform the security team has just adopted, instead of the existing tooling. Neither is aware of the other's statement. How should the architect handle this? (Choose two.)
Why does an architect consider the alliance partner ecosystem when positioning a solution?
A customer asks for a proposal to replace the environment an established workload runs on today. Which facts about the current arrangement most need establishing first? (Choose two.)
A customer's stated need is partly met by one offering and partly by another. How should the architect position them?
At handover, every requirement in a customer's brief has been demonstrated except one: failover to a second site, which cannot be shown until that site is built next quarter. How should the architect handle the handover?
A review of a customer's design produces five observations: a requirement about recovery time is unmet, the naming convention is inconsistent, one assumption about network capacity is unconfirmed, a component is a generation behind the current release, and installation is planned to be carried out by the customer's own team. Which observations should be raised as findings requiring action before commitment? (Choose two.)
A healthcare provider is replacing an ageing patient-records platform. It tells the architect that records must stay under its own governance, that clinicians need the system available during a network outage at any single site, and that its IT team has no capacity to take on a new operating model this year. Which characteristics must the positioned offering demonstrate? (Choose three.)
A customer asks for a recommendation to support a seasonal workload that runs heavily for two months and is close to idle for the rest of the year. A colleague proposes the offering the team most often sells, on the grounds that it is well proven with other customers. What is the weakness in that reasoning?
An architect intends to include a component from an alliance partner in a customer solution. What should be established before it appears in the proposal?
Adding a partner component to a solution introduces something the customer's operations team must account for. What is it?
A customer states two requirements that pull against each other: everything must be recoverable within a very short window after a failure, and the total spend must stay inside a fixed cap that will not cover full duplication. How should the architect proceed?
A customer is standing up a new analytics workload and has told the architect that its networking estate is being refreshed at the same time, that its analytics team already works with a specific software vendor, and that whatever is proposed has to be supportable by the customer's existing operations process. Which considerations belong in positioning the workload alongside the wider ecosystem? (Choose two.)
A customer’s private cloud has reached the limit of its available capacity, and a development team’s request cannot be met. What does this tell the customer?
What does a customer most need a proposal to make clear about an expansion?
A customer is attracted by managing its whole estate consistently but has not considered what adopting it involves. What should the architect tell them it will require? (Choose two.)
An architect is combining elements whose refresh cycles fall in different years. Why does this matter to the customer?
A start-up expects its user numbers to grow substantially over two years but cannot say how quickly. It has limited capital, a small engineering team that would rather build product than run infrastructure, and no regulatory constraint on where its data sits. Which characteristics should the positioned offering demonstrate? (Choose two.)
While reviewing another team's design, an architect finds that one of the customer's stated requirements can be read in two ways, and that the design satisfies only one of them. What should the review record?
A customer with workloads spread across edge sites, its data centre and a public cloud says it cannot tell where its capacity is being consumed, and wants to reduce waste. What should be addressed first?
A review finds that a design meets every requirement but leaves one low-likelihood failure unmitigated, and mitigating it would roughly double the cost. How should this be reported?
A customer opens a conversation by naming the specific offering it intends to buy, before describing any requirement. What is the appropriate response?
A customer states a requirement that cannot be met by any available arrangement within their stated budget. What is the architect's obligation?
An architect wants to propose expanding a customer's deployed solution. What evidence makes the proposal most credible to the customer?
A customer's proposed solution depends on a component supplied by an alliance partner, on a network refresh scheduled for the same quarter, and on a data migration the customer's own team will perform. The customer has asked what could delay the launch. Which dependencies most deserve to be called out? (Choose two.)