An expansion would add a demanding new workload to a customer's existing solution, which currently runs with modest headroom and supports a business-critical process. What must the proposal address that a new-build proposal would not?
A.
The total cost of the additional capacity over the life of the solution.
B.
Whether the new workload is a good technical fit for the offering being extended.
Option C is correct. Unlike a greenfield deployment, expansion must protect production workloads already on the shared platform. Assess interference with capacity, performance, recovery and stability before adding a demanding new workload. Executive-facing solution proposals must connect recommendation, justification, expected benefits and delivery approach. Architectural assumptions and trade-offs should remain transparent, and the plan should show how the customer will accept each material milestone. None of the other options supplies the same direct response to the stated constraint; each would require separate justification before becoming a valid design decision. The recommendation should therefore be recorded as a requirement-led technical decision with measurable success conditions. Any proposed deviation or dependency must be resolved through customer-approved change management before the solution is declared complete. A strong expansion proposal begins with evidence from the installed solution and a clearly described future operating state. Quantify the additional business outcome, delivery dependencies, customer obligations, resource impact and lifecycle consequences rather than listing more products.
Study Guide Reference: HPE Edge-to-Cloud Fundamentals — Prepare a Proposal to Grow an Installed Solution or Expand to Other Solutions; Presenting an HPE Solution.
Contribute your Thoughts:
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