An architect is tasked with creating a design for a vSphere-based solution.
Reviewing requirements with the security team, the architect makes the following design decision:
ESXi hosts in the environment will enable shell sandbox for SSH connections and the local ESXi shell
What is an implication of the design decision to enable shell sandboxing?
Answer : A
When the shell sandbox is enabled on ESXi hosts, it restricts the execution of commands within the shell to ensure that only authorized or safe commands are allowed. This provides a level of isolation that limits the potential for accidental or malicious commands to be run in the shell, enhancing security while still providing necessary administrative access.
An architect is documenting the design for a new vSphere cluster. The customer provides the following information:
All ESXi hosts will use hardware from the same vendor
All ESXi hosts will be monitored for hardware related issues using the vendor's monitoring tooling
The vendor's monitoring tooling provides a plugin for vCenter to allow the hardware status to be visible
The customer also informs the architect of the following requirements:
Workloads must be automatically relocated to other hosts in the event that a host hardware is marked as degraded.
Workloads must be automatically restarted on other hosts in the event of a host failure.
What should the architect include in the design to meet these requirements?
Answer : D
To meet the customer requirements, we need to address the two specific scenarios:
Workloads must be automatically relocated to other hosts in the event that a host hardware is marked as degraded:
This requirement can be fulfilled by Proactive HA. Proactive HA is a feature of vSphere HA that works in conjunction with hardware health monitoring tools, such as the vendor's plugin for vCenter. When the vendor's monitoring tool marks a host as degraded (due to hardware issues), Proactive HA can automatically trigger the migration of workloads to other hosts, based on the Automation Level configuration.
Workloads must be automatically restarted on other hosts in the event of a host failure:
This can be managed using vSphere HA with the setting to restart VMs when a host fails. This ensures that in the event of a host failure, workloads are automatically restarted on available hosts in the cluster.
By enabling Proactive HA with an Automation Level of Automated, the architect ensures that degraded hosts are automatically handled (through workload migration) without manual intervention.
An architect is designing a new vSphere solution. The solution will be used to host workloads that have multiple dependencies. The customer provides the following information regarding the workloads:
Workload 1: Self-Service Portal
Workload 2: Database
Workload 3: Identity Broker
Workload 4: Reporting Tool
Workload 5: Management Tool
Application A is formed of workloads 1 and 2 and has a dependency on workload 3
Application B is formed of workloads 2 and 4 and has a dependency on workload 3
Application C is formed of workload 5 and has a dependency on workload 4
How should the architect document the vSphere HA requirements to ensure that all of the applications can be recovered in the event of a host failure while observing the dependencies?
Answer : C
The goal here is to ensure that, in the event of a host failure, the workloads are restarted in the correct order based on their dependencies:
Workload 3 (Identity Broker) is required by both Application A and Application B as a dependency. It needs to be set to High Restart Priority, ensuring that it is restarted before the other dependent workloads.
Workload 4 (Reporting Tool) is required by Application B and Application C, so it should be set to High Restart Priority to ensure it is available before the other dependent workloads (like Workload 5).
Workload 5 (Management Tool) is required by Application C and should have a Medium Restart Priority, meaning it will be restarted after Workload 4.
Workloads 1 and 2 (Self-Service Portal and Database) have Low Restart Priority because they are dependent on Workload 3 (and Workload 4), but they do not have further critical dependencies after Workload 3, so they should be restarted last in the event of a failure.
This setup ensures that all applications can be recovered properly in the event of a host failure, with each workload restarting in the correct order to maintain the application dependencies.
A company has a requirement that all production applications must have a maximum tolerable downtime (MTD) of one hour per month.
Which statement would be included in the physical design to support this requirement?
Answer : B
To meet the requirement of a maximum tolerable downtime (MTD) of one hour per month for production applications, the solution must ensure high availability and quick recovery of virtual machines (VMs) in the event of a host failure. Enabling vSphere High Availability (HA) with the Host Failure Response set to Restart VMs will automatically restart VMs on other hosts within the cluster in the event of a host failure. This minimizes downtime and helps meet the MTD requirement by ensuring minimal disruption to production workloads.
An architect is designing the access management component of a vSphere-based solution. During a requirements gathering workshop, the customer states that the architecture must use a centralized user authentication solution.
The architect decides that an Open Lightweight Directory Access Protocol (OpenLDAP) solution would meet the requirement. The security team intervenes and requires that the solution use the corporate Active Directory Domain Services solution.
At which point did the architect's design become constrained?
Answer : D
The design became constrained when the customer required the use of the corporate Active Directory Domain Services (AD DS) solution. The security team's intervention and insistence on using the corporate Active Directory effectively limited the options available for the authentication solution, as OpenLDAP was no longer a valid choice. At this point, the solution's scope was restricted to ensure compatibility with the customer's existing Active Directory infrastructure, which imposed a specific requirement on the design.
An architect is tasked with designing a new workload domain in an existing VMware Cloud Foundation environment. The customer requirement is to physically separate the NSX host overlay network traffic from other management networks flows.
Which design decision should the architect make to meet this requirement?
Answer : B
To physically separate the NSX host overlay network traffic from other management network flows, the architect should use multiple physical adapters. This approach allows for the segmentation of different types of network traffic by assigning them to separate physical adapters, ensuring that the overlay network traffic used by NSX does not interfere with management traffic. This helps in maintaining optimal performance and security by isolating these network types at the physical level.
An architect is responsible for the following customer considerations in a hardware refresh:
Capacity planning will ensure that the environment does not exceed 70% of peak-average utilization on deployment.
CPU purchases will favor clock speed and last level cache over cores per socket.
Additional ESXi hosts will be added to the cluster when CPU or memory utilization exceeds 70% for 3 consecutive business days.
Path Selection policy will be set to round robin and set to switch paths with every SCSI command.
vCPU to pCPU ratio may not exceed 5:1.
What are three considerations when designing for performance? (Choose three.)
Answer : B, E, F
vCPU to pCPU ratio may not exceed 5:1.
This ensures that the virtual CPU (vCPU) allocation is balanced with the physical CPU (pCPU) resources. A ratio that exceeds 5:1 can lead to CPU contention, negatively impacting performance. By maintaining this ratio, the architect ensures that the workloads have sufficient CPU resources for optimal performance.
CPU purchases will favor clock speed and last level cache over cores per socket.
This is an important performance consideration. Choosing CPUs with higher clock speed and larger last-level cache (LLC) ensures that workloads requiring higher single-threaded performance are optimized. This decision favors workloads that benefit from faster CPU processing and larger cache sizes, improving overall performance.
Additional ESXi hosts will be added to the cluster when CPU or memory utilization exceeds 70% for 3 consecutive business days.
This performance-related decision ensures that the environment remains responsive under load. Adding additional hosts when resource utilization exceeds thresholds helps prevent bottlenecks and ensures continued optimal performance by distributing workloads across more physical hosts.