VMware 2V0-33.22 Practice Test - Questions Answers, Page 10

ustomer responsibility "Security in the Cloud" – Customers are responsible for the deployment and ongoing configuration of their SDDC, virtual machines, and data that reside therein. In addition to determining the network firewall and VPN configuration, customers are responsible for managing virtual machines (including in guest security and encryption) and using VMware Cloud on AWS User Roles and Permissions along with vCenter Roles and Permissions to apply the appropriate controls for users.

The responsibility for the encryption of virtual machines in VMware Cloud lies with the customer. The customer is responsible for configuring and managing any encryption or security related settings and configurations in the virtual machines, such as disk encryption or the configuration of security protocols. The VMware Cloud Provider Partner (VCPP) is responsible for the overall security of the cloud environment [1][2], including the encryption of data at rest, but the customer is responsible for configuring and managing the encryption settings within their virtual machines.

Reference: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc- aws.encryption/GUID-6F6921CA-44D6-4D9D-B0C0-12C18A545B7C.html

A cloud administrator needs to deploy the vSphere Replication virtual appliance and the Site Recovery manager virtual appliance when protecting a VMware Cloud on AWS software-defined data center (SDDC) with VMware Site Recovery.The vSphere Replication virtual appliance is responsible for replicating the virtual machines from the source to the target site. Site Recovery Manager virtual appliance acts as the central management and orchestration platform for the entire disaster recovery process.Reference: https://docs.vmware.com/en/VMware-Site-Recovery/index.htmlIn order to protect a VMware Cloud on AWS software-defined data center (SDDC) with VMware Site Recovery [1][2], a cloud administrator needs to take the following two steps: A) Deploy the vSphere Replication virtual appliance - This can be done by logging into the vSphere Client, navigating to the vCenter Server, and then selecting the Deploy OVF Template option. From here, the cloud administrator can upload the OVF template for the vSphere Replication appliance and configure it.B) Connect the Site Recovery manager instance on the protected recovery site - This involves logging into the Site Recovery Manager (SRM) and setting up the connection between the protected recovery site and the SRM instance. This can be done by going to the SRM dashboard and then selecting the Connect Remote Site option.

Reference:

[1] https://docs.vmware.com/en/VMware-Site-Recovery/services/vmc-dr-deployment/GUID- DBF6CD69-6F7E-47E2-9417-91D5C5F5AC5E.html

[2] https://docs.vmware.com/en/VMware-Site-Recovery/services/vmc-dr-deployment/GUID- 1C8B7BCA-D4BE-4EAF-9A8A-4B42E2B7236A.html

(Reference: https://docs.vmware.com/en/VMware-Cloud-on- AWS/services/com.vmware.vcloud.admin.doc/GUID-3568D3B3-ACFE-41F1-A966- 5D4784F8A7A0.html) To request access to the VMware Cloud on AWS service, the cloud administrator must log in to the VMware Cloud Console and fill out the New Subscription Request form. Once the form is filled out and submitted, the cloud administrator will receive an email with instructions on how to access the VMware Cloud on AWS service.The cloud administrator will also need to have the Administrator role in the VMware Cloud on AWS service in order to gain access. The Administrator role allows the cloud administrator to access the VMware Cloud on AWS service, view the services available in the VMware Cloud on AWS console, and manage the resources in the SDDC.Reference: [1] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/VMware-Cloud-on- AWS-Outposts/GUID-access.html

According to the VMware official documentation, in order to optimize scaling for full disaster recovery in a VMware Cloud on AWS environment, it is necessary to configure an Elastic DRS policy and select 'Optimize for Rapid scale-out' as the policy type. This option allows for a rapid increase in the number of hosts within the cluster, which is necessary for full disaster recovery. For more information, please refer to the VMware Cloud on AWS Disaster Recovery Guide, which can be foundhere: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/VMware-Cloud-on-AWS- Disaster-Recovery-Guide.html.

The two use cases that can be met with VMware Cloud on Dell EMC and VMware Cloud on AWS Outposts are Option C: Applications needing local data processing and/or low latency integrations, and Option D: Critical workloads that use restricted data.VMware Cloud on Dell EMC and VMware Cloud on AWS Outposts both provide local data processing and low latency integrations, making them ideal for applications that require quick and efficient access to data.

Additionally, the highly secure infrastructure of both solutions make them a great choice for critical workloads that use restricted data.For more information, please refer to the official VMware documentation on VMware Cloud on DellEMC:

https://www.vmware.com/products/vmware-cloud-on-dellemc.html And the official VMwaredocumentation on VMware Cloud on AWS Outposts: https://www.vmware.com/products/vmware-cloud-on-aws-outposts.html

The best solution for enabling network extension from the cloud side to the on-premises data center in this scenario is to ensure that the on-premises environment has at least a VMware vSphere Distributed Switch with version 6.5 configured. This will enable the reverse L2E feature, which is necessary for extending the native layer 2 network segment from the cloud back into the on- premises data center. For more information on how to configure reverse L2E and extend a network segment from the cloud to the on-premises data center, please refer to the official VMware documentation here.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking- security/GUID-586C053D-9553-461E-B6A8-FF508C8F091C.html

Private L2 VPN: To migrate running VMs between SDDCs in different geographical locations.You use a private layer 2 (L2) VPN to extend an on-premises network to your cloud SDDC. This extended network is a single subnet with a single broadcast domain.

You can use L2 VPNs to migrate VMs to and from your cloud SDDC, for disaster recovery, or for dynamic access to cloud computing resources (often called cloud bursting).VM migrations across an L2 VPN support VLAN tagging and GENEVE frame encapsulation when migrating between a cloud SDDC to another SDDC.The L2 VPN tunnel extends layer 2 networks across geographic sites. VMs can move across sites (using vSphere vMotion) and keep the same IP addresses using an L2 VPN.

The three types of gateways that can be found in VMware Cloud on AWS are Option A: Distributed Tier-1, Option B: Standard Tier-1, and Option D: Compute Tier-1.Distributed Tier-1 gateways are used for secure access between on-premises networks and the VMware Cloud on AWS SDDC network. Standard Tier-1 gateways are used for secure access between the VMware Cloud on AWS SDDC network and the public internet. Compute Tier-1 gateways are used for secure access between the workloads running on the VMware Cloud on AWS SDDC and the public internet.For more information, please refer to the official VMware documentation on VMware Cloud on AWSGateways: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-1F2D1BFC-F5C7-4534-8B49-39F9D08E7F1A.htm