VMware vSAN 8.x Administrator — Question 29

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?

Answer options

• A. An assumption that the new platform will co-exist with the existing platforms for a period of time to allow workloads to be migrated in a phased approach
• B. An assumption that a complete mapping of application dependencies is not available
• C. A risk that the existing platforms are running Linux Operating Systems that are out of vendor support
• D. A requirement that the solution will provide the capability to migrate Kubernetes based workloads from the Public Cloud

Correct answer: A

Explanation

The correct answer, A, highlights the critical assumption that the new platform will need to operate alongside existing systems during the transition, ensuring a smooth migration process. Option B does not align with the objective of reducing risks related to incomplete documentation, while C is a risk but not an assumption relevant to the design documentation. Option D introduces a specific requirement that is not directly tied to the broader objectives of the organization.