A customer asks for a private cloud because it has read that it gives more control. Its workloads are short- lived, highly variable, and carry no residency or governance constraint. What should the architect say?

• A. The customer should be asked to reconsider once its workloads become more predictable.
• B. A private cloud is appropriate here, since retaining control is a legitimate reason to choose one.
• C. Control is real, but this workload profile is the one private cloud serves least economically.
• D. A private cloud should be avoided here, since it cannot host short-lived, highly variable workloads.

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

• A. Day-to-day upkeep demands very few staff hours.
• B. The engineering team can move the product elsewhere within two years without penalty.
• C. The environment is dedicated to the start-up, so no other tenant can affect it.
• D. Supply expands as the load actually rises.
• E. Capacity is reserved ahead of the user numbers the start-up expects, so nothing is ever held up.

What is the purpose of gathering requirements before designing a solution?

• A. To establish what the solution has to achieve before decisions about how are taken.
• B. To produce a record protecting both parties, should a dispute arise.
• C. To give the customer confidence that the engagement is being run methodically.
• D. To identify which of the vendor's offerings the customer is most likely to buy.

Reviewing a design, an architect concludes it meets every stated requirement, but that one requirement appears to rest on a misunderstanding that will cost the customer significantly. What should the review do?

• A. Record the design as deficient, since it will cost the customer more than necessary.
• B. Leave the requirement alone, since reviewing the brief, or amending it, is out of scope.
• C. Revise the requirement and re-review the design against the corrected version.
• D. Record that the design conforms, and raise the requirement separately as a question.