According to the Virtual Machine Affinity and Anti-Affinity - VMware Docs1, affinity and anti-affinity rules allow you to spread a group of virtual machines across different ESXi hosts or keep a group of virtual machines on a particular ESXi host. An affinity rule places a group of virtual machines on a specific host so that you can easily audit the usage of those virtual machines.
Containers are "a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another" 2. Containers can run on any virtual machine or physical server, and they can be moved between different hosts without affecting the application functionality.
A firewall is "a device or software that monitors and controls the incoming and outgoing network traffic based on predefined rules" 3. A firewall can help protect a cloud environment from unauthorized access and malicious attacks, but it does not affect the placement of virtual machines on hosts.
Load balancers are "devices or software that distribute network or application traffic across a number of servers" . Load balancers can help improve the performance and availability of a cloud environment by distributing the workload among multiple servers, but they do not affect the placement of virtual machines on hosts.
Based on this information, I think the best answer to your question is C. Affinity rules. Affinity rules can help the pharmaceutical company ensure compliance by placing the application on its own virtual machine and keeping it on the same host. This way, the company can easily audit the usage of the application and avoid any changes in the hardware configuration.

DNS (Domain Name System) is a service that translates human-friendly domain names into IP addresses that can be used to communicate over the Internet1. However, DNS queries and responses are usually sent in plain text, which means that anyone who can intercept the network traffic can see the domain names that the users are requesting. This poses a threat to the confidentiality and privacy of the users and their online activities2.
To ensure confidentiality between the DNS server and an upstream DNS provider, a technician should configure DOH (DNS over HTTPS). DOH is a protocol that encrypts DNS queries and responses using HTTPS (Hypertext Transfer Protocol Secure), which is a secure version of HTTP that uses SSL/TLS (Secure Sockets Layer/Transport Layer Security) to protect the data in transit3. By using DOH, the technician can prevent eavesdropping, tampering, or spoofing of DNS traffic by malicious actors3.
The other options are not the best steps to ensure confidentiality between the DNS server and an upstream DNS provider:
Option A: Enable DNSSEC (DNS Security Extensions). DNSSEC is a set of extensions that add digital signatures to DNS records, which can be used to verify the authenticity and integrity of the DNS dat a. DNSSEC can prevent DNS cache poisoning attacks, where an attacker inserts false DNS records into a DNS server's cache, redirecting users to malicious websites. However, DNSSEC does not encrypt or hide the DNS queries and responses, so it does not provide confidentiality for DNS traffic2.
Option B: Implement single sign-on (SSO). SSO is a mechanism that allows users to access multiple services or applications with one set of credentials, such as a username and password. SSO can simplify the authentication process and reduce the risk of password compromise or phishing attacks. However, SSO does not affect the communication between the DNS server and an upstream DNS provider, so it does not provide confidentiality for DNS traffic.
Option D: Set up DNS over SSL (DNS over Secure Sockets Layer). This option is not a valid protocol for securing DNS traffic. SSL is a deprecated protocol that has been replaced by TLS (Transport Layer Security), which is more secure and robust. The correct protocol for encrypting DNS traffic using SSL/TLS is DOH (DNS over HTTPS), as explained above.

Detailed
B . 50%: In a two-disk mirror (RAID 1), one disk is used for redundancy. Therefore, only 50% of the total disk capacity is available for storage.
References:
CompTIA Cloud+ CV0-003 Study Guide Chapter 12: Storage in Cloud Environments.

Infrastructure as code (IaC) is a method of provisioning and managing cloud resources using code or scripts, rather than manual processes or GUI tools. This allows for automation, consistency, scalability, and version control of the infrastructure layer. This would be the best option to deploy a solution to automate new application releases that come from the development team without modifying any configurations in the application code. Reference: CompTIA Cloud+ Certification Exam Objectives, Domain 3.0 Maintenance, Objective 3.4 Given a scenario, implement automation and orchestration to optimize cloud operations.

A virtual graphics processing unit (vGPU) is a type of hardware or software that enables a VM to use the physical GPU resources of the host or server for graphics-intensive tasks. Upgrading the vGPU is most likely to solve the issue of VDI performance being slow since the images were upgraded from Windows 7 to Windows 10, as it can provide more graphics processing power and memory for the VMs. Upgrading the vGPU can also improve the user experience and productivity, as it can enhance the display quality and responsiveness of the VDI environment. Reference: CompTIA Cloud+ Certification Exam Objectives, page 11, section 1.6