A customer adopted a private cloud so that teams would stop waiting for environments without capacity being wasted. A year in, it asks how to tell whether the environment is delivering that. What should the architect point them at?
A.
The number of environments created and still running, rather than how long anyone waited for them.
B.
How the platform's running cost compares with the equivalent public capacity.
C.
The proportion of requests that required an exception to be granted.
D.
How long teams now wait for an environment, and how much of the pool is in use.
Option D is correct. Measure the two promised private-cloud outcomes directly: time from approved request to usable environment, and utilisation of the resource pool. Counts of instances and comparisons with external list prices alone do not prove success. Before positioning a private cloud, analyse the expected usage profile and operating model. Dedicated infrastructure can favour sustained demand, whereas unpredictable peaks may call for carefully evaluated elastic or hybrid capacity; governance and location requirements remain fundamental. Alternatives based on product preference, unchecked scope changes or deferred validation would weaken the requirement-to-design traceability on which the recommendation depends. Where implementation work follows, document the responsible owner, acceptance test and escalation path. A technically correct design still needs controlled delivery and a supportable operating model to deliver the business outcome. Private-cloud architecture combines dedicated organisational resources with automated provisioning, standardised service definitions and central governance. Self-service shortens fulfilment time but is still bounded by real capacity, operating policies, support responsibilities and the lifecycle of the infrastructure underneath.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit