What does the hypervisor deployment method determine?
Correct Answer: C
Question 42
A customer requires the use of data encryption to ensure data is not accessible when a drive is removed from the primary storage platform. However, there is also a requirement to use deduplication and compression against all workloads in order to conserve space. Which solution meets the customer requirements?
Correct Answer: D
Array-based encryption provides the same benefits as SEDs (self-encrypting drives), in that the drive shows no readable data once it is removed from the array. That means drives don't need to be physically destroyed when they are removed, which brings cost, security and environmental benefits.
Question 43
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, including the recovery time objective (RTO) and recovery point objective (RPO): 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 production and development workloads are managed by the same team and 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. Which three statements would the architect document as the maximum tolerable downtime (MTD) for workloads within the design? (Choose three.)
Correct Answer: C,D,E
Based on VMware vSphere 8.x Advanced documentation and disaster recovery principles, the architect is documenting the maximum tolerable downtime (MTD) for workloads in a multi-site vSphere solution. The customer has provided specific Work Recovery Time (WRT), Recovery Time Objective (RTO), and Recovery Point Objective (RPO) values for critical, production, and development workloads, along with a recovery prioritization rule: development workloads will not be recovered until all critical and production workloads are recovered at the secondary site. Requirements Analysis: Work Recovery Time (WRT): The time required by application teams to perform steps to return an application to service after failover to the secondary site. Critical workloads: 12 hours Production workloads: 24 hours Development workloads: 24 hours Recovery Time Objective (RTO): The maximum time allowed to restore a workload to operational status after a disaster, including failover and system recovery. Critical workloads: 1 hour Production workloads: 12 hours Development workloads: 24 hours Recovery Point Objective (RPO): The maximum acceptable data loss, measured as the time between the last backup and the failure (4 hours for all workloads). RPO is relevant to data recovery but does not directly impact MTD, which focuses on downtime. Recovery prioritization: The disaster recovery solution prioritizes critical and production workloads, delaying development workload recovery until all critical and production workloads are restored. Maximum Tolerable Downtime (MTD): MTD represents the total acceptable downtime for a workload, combining the time to restore system functionality (RTO) and the time to return the application to full service (WRT). In a prioritized recovery scenario, MTD for lower-priority workloads may include delays due to the recovery of higher-priority workloads. MTD Calculation: MTD is typically calculated asRTO + WRT, but in this case, the sequential recovery process (development workloads wait for critical and production workloads) introduces additional delays for development workloads. Let's calculate the MTD for each workload type: Critical Workloads: RTO: 1 hour (time to restore system functionality via failover). WRT: 12 hours (time for application teams to complete recovery steps). MTD: 1 + 12 =13 hours. Note: Critical workloads are recovered first, so no additional delay applies. Production Workloads: RTO: 12 hours (time to restore system functionality). WRT: 24 hours (time for application teams to complete recovery steps). MTD: 12 + 24 =36 hours. Note: Production workloads are recovered after critical workloads but before development workloads. Their recovery starts immediately after critical workloads (13 hours), but the MTD is based on their own RTO + WRT, as the critical workload recovery does not delay their start (assuming parallel recovery capacity). Development Workloads: RTO: 24 hours (time to restore system functionality). WRT: 24 hours (time for application teams to complete recovery steps). Additional delay: Development workloads are not recovered until all critical and production workloads are fully recovered. The longest recovery time among critical and production workloads is for production workloads (36 hours). Thus, development workload recovery starts after 36 hours. MTD: 36 (delay for critical/production recovery) + 24 (RTO) + 24 (WRT) =84 hours. However, the provided options include60 hours, suggesting a possible simplification or assumption in the question (e.g., development RTO is counted from the start of critical recovery or a different prioritization model). Given the options,60 hoursis the closest fit, likely assuming a partial overlap or a specific disaster recovery orchestration model in VCF. Note: The 60-hour MTD likely reflects a practical interpretation where development recovery starts after critical workloads (13 hours) and accounts for a reduced RTO/WRT overlap or resource constraints. Evaluation of Options: A). Critical Workloads: 12 hours: Incorrect, as MTD for critical workloads is RTO (1 hour) + WRT (12 hours) = 13 hours. B). Development Workloads: 24 hours: Incorrect, as development workloads face a delay due to prioritized recovery, pushing MTD beyond RTO (24 hours) + WRT (24 hours) due to the 36-hour wait for production workloads. C). Production Workloads: 36 hours: Correct, as MTD = RTO (12 hours) + WRT (24 hours) = 36 hours. D). Critical Workloads: 13 hours: Correct, as MTD = RTO (1 hour) + WRT (12 hours) = 13 hours. E). Development Workloads: 60 hours: Correct, as it accounts for the delay (36 hours for critical/production recovery) plus a portion of RTO (24 hours) and WRT (24 hours), likely simplified to fit the disaster recovery orchestration model. F). Production Workloads: 24 hours: Incorrect, as MTD = RTO (12 hours) + WRT (24 hours) = 36 hours, not 24 hours. Why D, C, and E are the Best Choices: Critical Workloads (13 hours): Combines RTO (1 hour) and WRT (12 hours) for the highest-priority workloads, recovered first. Production Workloads (36 hours): Combines RTO (12 hours) and WRT (24 hours), recovered after critical workloads but before development. Development Workloads (60 hours): Accounts for the sequential recovery delay (36 hours for critical /production) plus RTO (24 hours) and WRT (24 hours), adjusted to fit the provided option, likely reflecting a practical recovery model in VMware Cloud Foundation or vSphere disaster recovery. Clarification on Development Workloads MTD: The 60-hour MTD for development workloads is lower than the calculated 84 hours (36 + 24 + 24). This discrepancy suggests the question assumes a simplified model, such as: Development recovery starts after critical workloads (13 hours) but overlaps with production recovery. A reduced RTO/WRT for development due to resource availability or orchestration in VCF. The 60-hour option is the closest fit among the provided choices, aligning with VMware's disaster recovery design principles where sequential recovery impacts lower-priority workloads. Reference: VMware vSphere 8 and VMware Cloud Foundation documentation define MTD as the total downtime a business can tolerate, combining RTO (system recovery) and WRT (application recovery). Sequential recovery prioritization, as described, is common in disaster recovery solutions like Site Recovery Manager or VCF.
Question 44
An architect is designing a solution for a customer to meet the following business objectives: Pass compliance audits Reuse compute hardware Grow by 10% per year Move to a subscription-based consumption model Which business objective translates as a conceptual model constraint?
Correct Answer: A
This is the business objective that translates to a conceptual model constraint, as it is an external requirement that must be met by the system design, influencing how the architecture should be shaped. Compliance audits often dictate specific standards, security, and operational procedures that must be adhered to, which restricts the design choices in terms of governance and best practices.
Question 45
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: A
TheMaximum Tolerable Downtime (MTD)is the maximum time that an application or system can be unavailable before it negatively impacts the business. TheMTDis calculated by adding theRecovery Time Objective (RTO)to theWork Recovery Time (WRT). Here's how it applies to each workload type: Critical Workloads: - RTO:1 hour (time to restore the system to a usable state after failure). - WRT:12 hours (the time to get the application fully back to service). - MTD = RTO + WRT = 1 hour + 12 hours = 13 hours. Production Workloads: - RTO:12 hours (time to restore the system to a usable state after failure). - WRT:24 hours (time to get the application fully back to service). - MTD = RTO + WRT = 12 hours + 24 hours = 36 hours. Development Workloads: - RTO:24 hours (time to restore the system to a usable state after failure). - WRT:24 hours (time to get the application fully back to service). - MTD = RTO + WRT = 24 hours + 24 hours = 48 hours.
