Valid 3V0-21.23 Dumps shared by ExamDiscuss.com for Helping Passing 3V0-21.23 Exam! ExamDiscuss.com now offer the newest 3V0-21.23 exam dumps, the ExamDiscuss.com 3V0-21.23 exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com 3V0-21.23 dumps with Test Engine here:
An architect is documenting the design for a new multi-site vSphere solution. The customer has informed the architect that the workloads hosted on the solution are managed by application teams, who must perform a number of steps to return the application to service following a failover of the workloads to the secondary site. These steps are defined as the Work Recovery Time (WRT). The customer has provided the architect with the following information about the workloads: Critical workloads have a WRT of 12 hours Production workloads have a WRT of 24 hours Development workloads have a WRT of 24 hours All workloads have an RPO of 4 hours Critical workloads have an RTO of 1 hour Production workloads have an RTO of 12 hours Development workloads have an RTO of 24 hours The customer has also confirmed that the Disaster Recovery solution will not begin the recovery of the development workloads until all critical and production workloads have been recovered at the secondary site. What would the architect document as the maximum tolerable downtime (MTD) for each type of workload in the design?
Correct Answer: C
vSphere Lifecycle Manager (vLCM) is used to manage ESXi host configurations and software versions in a consistent and streamlined manner. In this case, the architect needs to account for the heterogeneous hardware across two sites (Intel and AMD-based servers). Since Intel and AMD processors are incompatible for remediation with a single vSphere Lifecycle Manager image, the different processor architectures should be grouped by site (not across sites). Within each site, vLCM can manage a single image per processor architecture, ensuring that each site's hosts with compatible processors are remediated consistently. Intel-based servers will be managed with one image and AMD-based servers with another image, but they can be managed in separate sites. This approach avoids the issue where heterogeneous hardware with different processor types would need separate images. By keeping them within the same site, the architecture simplifies the lifecycle management and meets the requirement for minimizing clusters and ensuring service availability during upgrades.