2V0-33.22 Practice Exam Questions with Answers VMware Cloud Professional Certification

Port mirroring is a VMware Cloud tool that an administrator can use to forward all the monitored traffic to a network appliance for analysis and remediation. The network appliance can then analyze the mirrored traffic and take the appropriate remedial action. Port mirroring can also be used to identify and troubleshoot network issues, as well as monitor network activities.

Port mirroring lets you replicate and redirect all of the traffic coming from a source. The mirrored traffic is sent encapsulated within a Generic Routing Encapsulation (GRE) tunnel to a collector so that all of the original packet information is preserved while traversing the network to a remote destination.

Port mirroring is used in the following scenarios:

• Troubleshooting - Analyze the traffic to detect intrusion and debug and diagnose errors on a network.
• Compliance and monitoring - Forward all of the monitored traffic to a network appliance for analysis and remediation.

Port mirroring includes a source group where the data is monitored and a destination group where the collected data is copied to. The source group membership criteria require VMs to be grouped based on the workload such as web group or application group. The destination group membership criteria require VMs to be grouped based on IP addresses. Port mirroring has one enforcement point, where you can apply policy rules to your SDDC environment.

The traffic direction for port mirroring is Ingress, Egress, or Bi Directional traffic:

• Ingress is the outbound network traffic from the VM to the logical network.
• Egress is the inbound network traffic from the logical network to the VM.
• Bi Directional is the traffic from the VM to the logical network and from the logical network to the VM. This is the default option.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-3268A0D3-89D0-406F-B44F-156DD1A30E00.html

https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/index.html Tanzu Kubernetes Grid provides packaged services such as networking, authentication, ingress control, and logging that a production Kubernetes environment requires.

A VM storage policy is a set of rules that defines the storage requirements for a virtual machine or an object. A cloud administrator can create and apply different VM storage policies for different types of objects, such as virtual disks, ISO images, snapshots, etc1. Applying a new VM storage policy to an object will change its compliance status and trigger a reconfiguration task to move the object to a compatible datastore1.

Modifying the default VM storage policy will affect all the objects that use it, which may not be desirable. Recreating the ISO image is unnecessary and time-consuming. Attaching the ISO image to a virtual machine will not change its storage policy1.

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/certification/vmware-vcp-vmc-exam-guide.pdf

vCenter Mapping Mapping vCenters in a DR plan consists of selecting source vCenters that are registered to the protected site. Choosing a target vCenter for a Failover SDDC is simple; each SDDC contains a single vCenter instance. For VMware Cloud Disaster Recovery, keep in mind that a protected site can have multiple registered vCenters, but you can only map one vCenter on VMware Cloud on AWS per-DR plan. https://vmc.techzone.vmware.com/resource/introduction-vmware-cloud-disaster-recovery#inventory-and-resource-mapping https://vmc.techzone.vmware.com/resource/protection-groups-and-recovery-plans-vcdr#create-a-disaster-recovery-plan

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-8AE1DC05-46D1-410C-99F6-7687FEB876B5.html

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-0E34C56D-C49C-49B6-A9CF-FBFAF14A126C.html

To allow HTTPS access to a specific VM through the public Internet for VMware Cloud on AWS, the administrator should take the following two steps:

• Request a public IP address in the VMware Cloud console. This is required because the VM needs a public IP address to be reachable from the Internet1. The administrator can request a public IP address from the Networking & Security tab in the VMware Cloud console1. The public IP address is allocated from the AWS pool and is associated with the SDDC1.
• Configure a DNAT rule translating a public IP address to an internal IP address. This is required because the VM has an internal IP address assigned by the SDDC DHCP server, and the DNAT rule maps the public IP address to the internal IP address of the VM2. The administrator can configure a DNAT rule from the Networking & Security tab in the VMware Cloud console2. The DNAT rule must specify the public IP address as the source, the internal IP address as the destination, and the HTTPS service (TCP 443) as the applied to2. References: 1: Request a Public IP Address - VMware Docs, 2: Configure NAT Rules - VMware Docs

When deploying VMware Cloud on Dell EMC or VMware Cloud on AWS Outposts, the Dell or AWS guys will bring a populated rack to the on-prem DC to extend the private cloud. They will bring technisians on-site to carry, install and configure the devices. AWS Outposts rack hardware specs: https://aws.amazon.com/outposts/rack/hardware-specs/?nc=sn &loc=4 https://docs.vmware.com/en/VMware-Cloud-on-Dell-EMC/services/vmc.dell.emc.datasheet/GUID-9252D1FC-FE9C-4317-8EEB-4C019A21CAA9.html

• Total number of workloads. This determines how many hosts are needed in the VMware Cloud SDDC cluster.
• Total amount of available storage across all on-premises datastores. This determines how much storage capacity is needed in the VMware Cloud SDDC cluster.
• Average size of workload resources (CPU & RAM). This determines how much compute capacity is needed in the VMware Cloud SDDC cluster.

https://docs.vmware.com/en/VMware-Cloud/services/vmc-cloud-sizer-user/GUID-7CECF719-E56B-4830-84ED-77206A2A118D.html

"It is a good idea to periodically monitor the CPU usage of the host. This can be done through the vSphere Client, using the VMware vRealizeOperations management suite, or by using resxtop. Below we describe how to interpret resxtop" https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/vmc-aws-performance.pdf

• Use the VMware vSphere Client to connect to the VMware vCenter which manages the virtual machine and examine its performance statistics. You can use charts, alarms, and events to identify CPU bottlenecks or contention.
• Use the Troubleshooting Workbench in VMware vRealize Operations Cloud to look for potential evidence. You can use dashboards, alerts, metrics, logs, and recommendations to diagnose and resolve CPU performance issues.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/vmc-aws-performance.pdf

Customer 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

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 two VMware solutions that can meet the customer's requirement for a self-managed VDI solution are D. VMware Horizon and E. VMware Workspace ONE Access. VMware Horizon is a virtual desktop and application virtualization platform that enables customers to set up and deploy a virtual desktop infrastructure in any cloud environment. VMware Workspace ONE Access provides secure access to applications, data, and devices in any cloud environment.

A valid management network CIDR based on the requirements is 10.1.0.0/20, as this provides a range of 4096 IP addresses, which is more than enough for 30 hosts. A /23 CIDR only provides 512 IP addresses, which is not enough for 30 hosts, while a /24 CIDR provides 256 IP addresses and a /16 CIDR provides 65,536 IP addresses, which is more than is needed for the 30 hosts.

https://blogs.vmware.com/cloud/2019/10/03/selecting-ip-subnets-sddc/

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-4D0D375F-C001-4F1D-AAB1-1789C5577A94.html

Tanzu CLI is a command-line interface used to create, scale, upgrade, and delete workload clusters that are part of the Tanzu Kubernetes Grid [1]. Tanzu CLI also allows you to manage the components of the Tanzu Kubernetes Grid [1], such as the Tanzu Kubernetes cluster and the Tanzu Supervisor cluster. It also provides access to the Tanzu Kubernetes Grid extensions [1], which allow you to extend the functionality of the Tanzu Kubernetes cluster.

https://docs.vmware.com/en/VMware-Tanzu-CLI/index.html

VMware NSX is a network virtualization and security platform that provides a range of features for creating and managing virtual networks, including the ability to create secure connections over the Internet between on-premises data centers and VMware Cloud software-defined data centers (SDDCs). NSX allows you to create logical networks that are isolated from the underlying physical infrastructure, providing enhanced security and flexibility. With NSX, you can create secure, encrypted connections between your on-premises data center and your VMware Cloud SDDC, allowing you to easily and securely connect your workloads and applications running in the cloud to your on-premises resources.

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-11C83D2A-A478-4823-B9B3-275AF6DD31CC.html

A protection group in VMware Cloud Disaster Recovery (VCDR) consists of members (virtual machines or VMs) and policies for snapshots. These policies define the consistent point-in-time copies of the VMs, which are used for disaster recovery. The protection group also includes virtual machine file system (VMFS) datastores, which are used to store the copies of the VMs, and VM customizations, which are used to customize the VMs. Clusters are not part of a protection group in VCDR.

Hybrid Linked Mode allows you to link your cloud vCenter Server instance with an on-premises vCenter Single Sign-On domain. https://docs.vmware.com/en/VMware-Cloud- on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-91C57891-4D61-4F4C-B580-74F3000B831D.html

Hybrid Linked Mode is the solution that meets the requirement of viewing and managing workloads across both an on-premises environment and a VMware Cloud on AWS SDDC. Hybrid Linked Mode allows customers to link their on-premises vCenter Server with their VMware Cloud on AWS vCenter Server and use a single interface to manage both environments1. Hybrid Linked Mode also enables customers to perform cold and live migrations of workloads between on-premises and cloud SDDCs2. Hybrid Linked Mode leverages the existing vCenter Single Sign-On domain and does not require any additional components or licenses1. References: 1: Hybrid Linked Mode - VMware Docs, 2: VMware Cloud on AWS Documentation

An extended network segment is required for a cloud administrator to create a virtual machine that requires layer 2 connectivity to an on-premises workload. Extended networks allow for the virtual machines to communicate directly with the on-premises workload while remaining isolated from the public cloud. This allows for the virtual machines to access the same services and workloads as the on-premises workloads while still remaining secure.

The throughput provided by a Google Cloud VMware Engine private cloud network is 100 Gbps. This allows for a high level of performance and scalability, and supports a variety of services and applications. Additionally, the private cloud network is secure and reliable, providing support for different authentication methods and encryption standards.

100Gb dedicated for cluster (vSAN + east-west) 4x mellanox connect-4 lx dual port 25GbE.

 Incident Management is responsible for handling customer incidents and ensuring customer satisfaction. Capacity Management is responsible for ensuring that the service is sized appropriately for customer needs and that the capacity is monitored to ensure that it meets customer requirements. VMware Tools management, Microsoft licensing management, and workload OS management are not part of the service management process.

What is a Hypervisor? | VMware Glossary

https://www.vmware.com/topics/glossary/content/hypervisor.html

VMware Cloud on AWS Operations Guide

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/vmc-aws-operations.pdf

What is a Bare Metal Hypervisor? | VMware Glossary

https://www.vmware.com/topics/glossary/content/bare-metal-hypervisor.html

"The VMware HCX on-premises deployment requires five IP addresses: two for the WAN appliance, two for the vMotion feature, and one for the management network." 

In this scenario, the cloud administrator is utilizing the vMotion feature of VMware HCX to migrate several dozen workloads from an on-premises location to a VMware public cloud. They are also stretching three networks for the migration. When using vMotion, two IP addresses will be needed per vMotioned virtual machine: one for the source and one for the target. For the migration of several dozen workloads, this will require several dozens of IP addresses. Additionally, the administrator is also utilizing the capabilities of the WAN appliance to optimize migration traffic. In order to optimize the traffic, one IP address will be needed for the WAN appliance on the on-premises site, and another IP address will be needed for the WAN appliance on the public cloud side. Therefore, the total number of IP addresses that need to be reserved for the on-premises deployment of VMware HCX is the number of IP addresses required for the virtual machines plus one IP address for the WAN appliance on the on-premises site plus another IP address for the WAN appliance on the public cloud side, which totals to five IP addresses.

https://blogs.vmware.com/management/2020/01/the-cloud-operating-model.html

Aligning and connecting people, process, and technologies across layers of the IT and business organizations is an important success factor for cloud deployments. https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/docs/vmw-idc-enabling-a-cloud-operating-model-for-software-defined-infrastructure.pdf

To deploy an instance of Azure VMware Solutions, an administrator must take the following two steps:

• Create a support request with Microsoft Azure Support to create a host quota. This is required because Azure VMware Solution hosts are dedicated bare-metal servers that are not shared with other customers1. The host quota determines the number and size of hosts that can be provisioned in a subscription1. The host quota can be requested for an eligible Azure plan, such as Microsoft Enterprise Agreement or Cloud Solution Provider2.
• Deploy and configure Microsoft Azure ExpressRoute. This is required because Azure VMware Solution uses ExpressRoute to connect the private cloud to the Azure virtual network and the on-premises network3. ExpressRoute provides a secure, high-bandwidth, and low-latency connection that enables seamless workload migration and hybrid cloud scenarios3. The administrator must deploy and configure an ExpressRoute circuit, a virtual network gateway, and a virtual network3. References: 1: Deploy and configure Azure VMware Solution, 2: Plan the Azure VMware Solution deployment, 3: Tutorial: Deploy an Azure VMware Solution private cloud

VMware Cloud on AWS GovCloud supports three types of network segments: routed, extended and disconnected.

Routed networks: Routed networks allow you to route traffic between the on-premises data center and the VMware Cloud on AWS environment using a VPN or AWS Direct Connect.

Extended networks: Extended networks allow you to extend the on-premises network to the VMware Cloud on AWS environment using VXLAN. This type of network allows you to extend the on-premises VLANs to the cloud environment, providing a seamless network extension.

Disconnected networks: Disconnected networks are used when there is no direct connectivity between the on-premises data center and the VMware Cloud on AWS environment. This type of network allows you to create isolated networks in the cloud environment for specific use cases, such as disaster recovery or testing.

https://docs.vmware.com/en/VMware-Cloud-on-AWS-GovCloud-(US)/services/vmc-govcloud-networking-security/GUID-7E79585B-1487-454A-90FE-BA82D3122C0E.html

VMware HCX Network Extension is a layer-two bridging function initiated at the source site1. It allows customers to extend their on-premises networks to a VMware Cloud SDDC without changing the IP addresses of the virtual machines2. When extending a network, a corresponding NSX segment is created at the destination site1. The network segment type that HCX Network Extension creates in the VMware Cloud SDDC is Extended2. This means that the network is stretched across both sites and the routing is handled at the source site2. The Extended network segment type preserves the network identity and connectivity of the virtual machines that are migrated or created on the extended segment at the remote site2. References: 1: Extending Networks Using VMware HCX, 2: About VMware HCX Network Extension

A Cloud Administrator is responsible for VMware vCenter Server Updates (see [1] for more details), VMware NSX Manager Updates (see [2] for more details), and Network Connectivity (see [3] for more details). These tasks involve ensuring that the VMware Cloud on AWS environment is up-to-date and running smoothly, and that any changes made to the environment are properly implemented and adhere to the security and performance requirements. Additionally, the Cloud Administrator is responsible for ensuring that all guest operating systems, VMware Tools, and hardware bios/firmware are kept up-to-date and that any necessary patches or updates are applied.

[1] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.administration/GUID-F86D6A1F-9985-4F29-9D56-F92600B2D48A.html [2] https://docs.vmware.com/en/VMware-NSX-T/services/nsxt-admin-guide.html [3] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-D2E2F9A9-8661-4BDB-A8A8-4D4F4F7C4E1A.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 found here: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/VMware-Cloud-on-AWS-Disaster-Recovery-Guide.html.

Management Gateway (MGW) The MGW is a Tier 1 router that handles routing and firewalling for vCenter Server and other management appliances running in the SDDC. Management gateway firewall rules run on the MGW and control access to management VMs. In a new SDDC, the Internet connection is labelled Not Connected in the Overview tab and remains blocked until you create a Management Gateway Firewall rule allowing access from a trusted source.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws- networking-security/GUID-2D31A9A6-4A80-4B5B-A382-2C5B591F6AEB.html