An architect is working with an organization on the creation of a new Private Cloud Platform. The organization has provided the following business objectives they wish to achieve with the new platform:
* Reduce the operating costs associated with running separate areas of hosting capacity and separate/duplicate systems.
* Reduce the risks, time, and effort associated with managing platforms that are out of vendor support.
* Reduce the operating costs associated with Public Cloud usage.
* Reduce the risks associated with having incomplete documentation for application inventory and dependency mappings.
They have grouped these business objectives into a set of use cases:
* Migration - Provide a platform that supports the migration of virtualized workloads from existing platforms.
* Containerization - Provide a platform that supports the deployment of containerized workloads.
* Centralization and Consolidation - Provide a central private cloud platform accessible to all relevant areas of the business.
When considering these objectives and use cases, what should the architect include in the design documentation as a part of the Conceptual Model?
The Conceptual Model in VCF outlines high-level assumptions and approaches to meet objectives. Option A, assuming 'co-existence with existing platforms for phased migration,' directly supports the Migration and Consolidation use cases, aligning with cost reduction and risk mitigation by enabling a controlled transition to the new VCF platform (e.g., using vMotion or HCX). Option B (Linux risk) is specific and unstated. Option C (dependency mapping) is a risk, not an assumption driving design. Option D (Kubernetes requirement) adds specificity beyond the stated objectives. A is foundational to VCF migration strategies.
Jolene
7 days ago