3V0-21-23 Practice Questions

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.

A Host Profile in vSphere allows for standardized host configurations across a cluster. Once a profile is

created and configured for a cluster, it can be applied to any host in that cluster, ensuring that the

configuration is consistent and easily replicated. In case of a host failure, the failed host can be

reinstalled from the VMware ESXi image, and the Host Profile can be applied automatically to bring

the host back to the desired configuration. This reduces the manual steps required for host recovery,

as the configuration will be automatically applied to the reinstalled host.

This is a business requirement because it aligns with corporate sustainability goals, focusing on

reducing environmental impact. It is a high-level goal that can drive design decisions but is not

directly related to the technical function or features of the system.

This is a business factor that will impact the design because rebranding the hotels in Mexico could

lead to changes in the company's requirements, such as the need for new branding, updated

infrastructure, or integration of new services. These factors will influence the design decisions

related to the edge hosting solution, potentially requiring special configurations or considerations for

these locations.

Performance refers to the system’s ability to meet the required service levels under various

conditions, including handling spikes in memory demand. In this case, the architect is ensuring that

the cluster can handle memory spikes of up to 20% without contention, which is a key performance

requirement to ensure that the workloads run optimally during peak business hours.

The ability to accommodate these memory demands without impacting performance directly aligns

with ensuring that the system performs as expected under peak load conditions.

Enable vSphere with Tanzu on a cluster deployed at a remote location.

VMware Cloud Foundation remote clusters can be deployed to extend the functionality of vSphere

with Tanzu to remote locations. This allows for containerized workloads to be managed and

orchestrated using the same tools as the primary environment, providing consistent management of

Tanzu clusters across multiple sites.

Provide resources for virtual machines at an edge location.

Remote clusters can be deployed at edge locations to provide computing resources for workloads

that need to run close to the data source. This use case is particularly useful for applications that

require low latency or need to process data locally before sending it to the central cloud

infrastructure.

The architect conducts workshops with stakeholders to gather business and technical requirements.

Workshops provide a collaborative environment where the architect can interact with key

stakeholders to gather both business and technical requirements. This approach helps ensure that

the final design aligns with the goals and needs of the business while considering the technical

constraints and capabilities.

The architect conducts multiple rounds of interviews with stakeholders, iteratively refining

requirements.

Multiple rounds of interviews allow the architect to gather input over time, refining the

requirements and addressing any evolving needs. This iterative approach ensures that the solution

meets the stakeholders' expectations and adapts as new information emerges.

This option aligns with the requirements for growth, scalability, and updating data protection

operations. Using vSAN (Virtual SAN) Ready Nodes provides a hyper-converged infrastructure that

combines storage and compute resources into a single platform, making it easy to scale both

compute and storage without increasing the data center footprint. It also eliminates the need for

traditional external storage arrays and allows for better data protection capabilities compared to the

agent-based approach.

The database must be backed up every day during the maintenance window of 1:00AM and 3:00AM.

This is a logical design requirement because it specifies the timing for the backup operations. It's

important to define backup schedules to align with the maintenance window, ensuring minimal

disruption to production workloads.

The database will be backed up using an API-based backup solution.

This is a logical design decision that specifies the method of backup. Using an API-based backup

solution is a modern, efficient way to ensure consistent and application-aware backups of databases.

Critical Workloads: 12 hours

For critical workloads, the recovery time objective (RTO) is 1 hour, and the work recovery time (WRT)

is 12 hours. Since the customer can tolerate a maximum of 12 hours to restore these workloads after

a disaster, the MTD for critical workloads is 12 hours.

Development Workloads: 24 hours

For development workloads, the RTO is 24 hours and the WRT is also 24 hours. Therefore, the MTD

for development workloads is 24 hours because it is the maximum time that the customer can

tolerate for these workloads to be unavailable.

Production Workloads: 24 hours

Production workloads have an RTO of 12 hours and a WRT of 24 hours. Since the disaster recovery

solution waits for the recovery of critical and production workloads before recovering development

workloads, the MTD for production workloads can be up to 24 hours, including the time to fully

recover both critical and production workloads.