VMware 2V0-33.22 VMware Cloud Professional Exam Practice Test

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

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.

VMware Multi-Cloud Vision enables customers to deliver a consistent management and operations layer across any cloud, and to modernize applications in the cloud of choice using the cloud-native services of that cloud provider. It does not run workloads in the cloud to eliminate security issues, standardize at the DevSecOps and infrastructure level, or reduce the number of developers to increase productivity.

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.

Planning your Azure VMware Solution deployment is critical for a successful production-ready environment for creating virtual machines (VMs) and migration. During the planning process, you'll identify and gather what's needed for your deployment. As you plan, make sure to document the information you gather for easy reference during the deployment. A successful deployment results in a production-ready environment for creating virtual machines (VMs) and migration.

In this how-to article, you'll do the following tasks:

Identify the Azure subscription, resource group, region, and resource name

Identify the size hosts and determine the number of clusters and hosts

Request a host quota for eligible Azure plan

Identify the /22 CIDR IP segment for private cloud management

Identify a single network segment

Define the virtual network gateway

Define VMware HCX network segments

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.

The Workspace ONE Access connector is used to synchronize groups and users from the internal Active Directory to the VMware Cloud Services Console. Additionally, the administrator should configure a SAML 2.0 Identity Provider to enable single sign-on (SSO) capability and secure access to the VMware Cloud Services Console.

The VMware technology that ensures availability of the VMs in your SDDC and uses multiple ESXi hosts to provide rapid recovery from outages and cost-effective high availability for applications is B. vSphere HA. vSphere HA is an agentless cluster-level availability solution that enables rapid recovery from outages and cost-effective high availability for applications. vSphere DRaaS, vSphere DPM, and vSphere eDRS are not suitable for this purpose.

The statement that most accurately describes the service features of VMware Cloud on Dell EMC is C. An SDDC includes a minimum of one rack with three hosts. You can add hosts to the rack, up to the maximum supported by the rack. An SDDC consists of a rack with a minimum of three hosts, which can then be expanded up to the maximum supported by the rack. VMware Site Recovery is not included as part of the initial service offering.

VMware Cloud on Dell EMC provides a service that enables customers to run their VMware-based workloads on Dell EMC's hardware, in a jointly-engineered and fully-supported environment. The service allows customers to deploy a fully-configured VMware SDDC on Dell EMC VxRail or VxRack SDDC systems, with the option to add more hosts to the rack as needed.

The VMware solution that offers long-term immutable point-in-time recovery options is VMware Cloud Disaster Recovery (CDR). CDR offers continuous data protection and point-in-time recovery options with up to 30 days of retention. It also provides a secure and immutable copy of your data that is stored in the cloud and can be used to recover from ransomware attacks.

To create a virtual machine template, you will need to configure the virtual machine hardware configuration, install the necessary applications, tools, and patches, and select the guest operating system. The template can also include vSphere tags and custom attributes to further customize the virtual machine. Additionally, the template can include virtual machine snapshots which will save the current state of the virtual machine and can be used to quickly restore the machine to the same state.

VMware Technical Support Guide

Publishing Applications with VMware Horizon 7

What is Server Virtualization? | VMware Glossary

A VMware Cloud software-defined data center (SDDC) uses a logical switching component called a Network Virtual Distributed Switch (N-VDS) or vSphere Distributed Switch (VDS) to provide layer 2 forwarding functionality [1][2]. A VDS is a network switch that provides centralized network configuration, management, and monitoring. It works with the NSX for vSphere data plane to provide layer 2 forwarding, packet filtering, and traffic monitoring services. A VDS is composed of multiple Segment Ports (which are like individual physical ports on a normal switch), Uplinks, and Transport Nodes. The Segment Ports are used to connect virtual machines to the VDS, while Uplinks are used to connect the VDS to physical networks. Transport Nodes are the physical switches that are associated with the VDS. For more information, see the official VMware documentation here: 

IPFIX (Internet Protocol Flow Information Export) is a standard for the format and export of network flow information for troubleshooting, auditing, or collecting analytics information. 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.

Use Traceflow to inspect the path of a packet. Traceflow traces the transport node-level path of a packet. The trace packet traverses the logical switch overlay, but is not visible to interfaces attached to the logical switch. In other words, no packet is actually delivered to the test packet’s intended recipients.

vRealize Log Insight is a log collection and analytics virtual appliance that enables administrators to collect, view, manage and analyze syslog data. Log Insight provides real-time monitoring of application logs, network traces, configuration files, messages and performance data.

Gateway firewalls are used to protect east-west traffic, while distributed firewalls control the I/O path to and from a VM's virtual NIC. Furthermore, gateway firewalls and distributed firewalls cannot share the same sets of rules and policies.

Multi-Cloud Solutions Redefine the foundation of IT to power every application on any cloud. With Multi-Cloud solutions from VMware, you can migrate to the cloud without recoding your apps, modernize your infrastructure, and operate consistently across the data center, the edge, and any cloud.

• 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.

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.

.

The cloud use case that describes the requirement of increasing the infrastructure capacity quickly to accommodate the rapid business growth is Maintain and Expand1. This use case is suitable for organizations that want to leverage the cloud to scale their existing data center capacity on demand, without changing their existing applications or processes1. VMware Cloud on AWS enables this use case by providing a consistent and compatible cloud platform that can be integrated with the on-premises VMware environment1. VMware Cloud on AWS allows customers to add or remove hosts from their SDDC cluster in minutes, using the Elastic DRS feature2. Customers can also use the VMware HCX service to migrate workloads between on-premises and cloud SDDCs seamlessly and securely3. References: 1: Use Cases for VMware Cloud on AWS, 2: Manage Elasticity in SDDC Clusters - VMware Docs, 3: Migrate Workloads Using VMware HCX - VMware Docs

CloudHealth by VMware is a cloud cost governance platform that provides budget management, cost reporting, and cost forecasting from a single platform. It provides comprehensive visibility and control to manage cloud costs in hybrid and multi-cloud environments. CloudHealth by VMware also provides cost optimization, resource optimization, and real-time alerting capabilities to help organizations make cost-effective decisions to reduce cloud costs.

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: &loc=4

The CloudAdmin role has the privileges necessary to create and manage SDDC workloads and related objects such as storage policies, content libraries, vSphere tags, and resource pools

The CloudAdmin role has the following privileges in SDDC Version 1.18.

ContentLibrary.AddCertToTrustStore

ContentLibrary.AddLibraryItem

ContentLibrary.CheckInTemplate

ContentLibrary.CheckOutTemplate

ContentLibrary.CreateLocalLibrary

ContentLibrary.CreateSubscribedLibrary

ContentLibrary.DeleteCertFromTrustStore

ContentLibrary.DeleteLibraryItem

ContentLibrary.DeleteLocalLibrary

ContentLibrary.DeleteSubscribedLibrary

ContentLibrary.DownloadSession

ContentLibrary.EvictLibraryItem

ContentLibrary.EvictSubscribedLibrary

ContentLibrary.GetConfiguration

ContentLibrary.ImportStorage

ContentLibrary.ProbeSubscription

ContentLibrary.ReadStorage

ContentLibrary.SyncLibrary

ContentLibrary.SyncLibraryItem

ContentLibrary.TypeIntrospection

ContentLibrary.UpdateConfiguration

ContentLibrary.UpdateLibrary

ContentLibrary.UpdateLibraryItem

ContentLibrary.UpdateLocalLibrary

ContentLibrary.UpdateSession

ContentLibrary.UpdateSubscribedLibrary

Compute Gateway (CGW) The CGW is a Tier 1 router that handles network traffic for workload VMs connected to routed compute network segments. Compute gateway firewall rules, along with NAT rules, run on the Tier 0 router. In the default configuration, these rules block all traffic to and from compute network segments (see Configure Compute Gateway Networking and Security).

The CGW is a Tier 1 router that handles network traffic for workload VMs connected to routed compute network segments. Compute gateway firewall rules, along with NAT rules, run on the Tier 0 router.

By default, the management gateway firewall is set to deny all traffic between the internet and vCenter Server. Verify that the appropriate firewall rules are in place.

The administrator can create an NSX firewall rule in the VMware Cloud data center that allows access to the vCenter from the on-premises data center. This would allow the VPN connection to connect to the vCenter, allowing the administrator to access and manage the VMware Cloud environment.

The problem could be that the new password is not synchronized with the password that is displayed for the Default vCenter user account. The administrator must make sure that the same password is used in both the vSphere Client and the VMware Cloud console in order for the user to access the account. Changing the password in one place does not automatically change it in the other, so this must be done manually.

vMotion Requirements for SDDCs With NSX:Networking speed and latency: Migration with vMotion requires sustained minimum bandwidth of 250 Mbps between source and destination vMotion vMkernel interfaces, and a maximum latency of 100 ms round trip between source and destination.

On-premises vSphere version: Your on-premises vSphere installation must be vSphere 6.7U2 or higher. See VMware Knowledge Base article 56991 for more information.

On-premises DVS version:  6.0 or higher.

On-premises NSX version: any

Note: SDDCs configured with NSX do not support hot vMotion to or from on-premises VXLAN encapsulated networks (NSX for vSphere) or Geneve Datacenter Overlay networks (NSX).

IPsec VPN: Configure an IPsec VPN for the management gateway.

See Configure a VPN Connection Between Your SDDC and On-Premises Data Center in the VMware Cloud on AWS Networking and Security guide.

Direct Connect: Direct Connect over a private virtual interface between your on-premise data center and your VMware Cloud on AWS SDDC is required for migration with vMotion.

See Using AWS Direct Connect with VMware Cloud on AWS.

Hybrid Linked Mode: Hybrid Linked Mode is required to initiate migration from the vSphere Client. It is not required to initiate migration using the API or PowerCLI.

See "Hybrid Linked Mode" in Managing the VMware Cloud on AWS Data Center.

L2 VPN: Configure a Layer 2 VPN to extend virtual machine networks between your on-premises data center and cloud SDDC. Routed networks are not supported. See VMware Cloud on AWS Networking and Security. VMware Cloud on AWS firewall rules Ensure that you have created the necessary firewall rules as described in Required Firewall Rules for vMotion.

On-premises firewall rules: Ensure that you have created the necessary firewall rules as described in Required Firewall Rules for vMotion.

Virtual machine hardware and settings: Ensure that these requirements are met for virtual machine hardware.

• Virtual machine hardware version 9 or later is required for migration with vMotion from the on-premises data center to the cloud SDDC.
• EVC is not supported in the VMware Cloud on AWS SDDC.
• VMs that are created in the cloud SDDC or that have been power-cycled after migration to the cloud SDDC can't be migrated back to the on-premises data center with vMotion unless the on-premises EVC baseline is Broadwell. You can relocate these VMs after powering them off, as long as their virtual machine hardware version is compatible with the on-premises data center.
• Migration of VMs with DRS or HA VM overrides is not supported. For more information on VM overrides, see Customize an Individual Virtual Machine.

Important: Source switch configurations (including NIOC, spoofguard, distributed firewall, and Switch Security) and runtime state are not applied at the destination as part of migration in either direction. Before you initiate vMotion, apply the source switch configuration to the destination network.

In order for a virtual machine to be migrated using VMware vSphere vMotion, the versions of VMware vSphere need to match between the on-premises data center and the cloud SDDC, and a Layer 2 connection needs to be configured between them. Additionally, cluster-level Enhanced vMotion Compatibility (EVC) must be configured in both the on-premises data center and the cloud SDDC. IPsec VPN and AWS Direct Connect do not need to be configured for the migration to occur.

One benefit of public cloud computing is cost savings on capital hardware expenses. Since the cloud provider owns and manages the hardware, the customer does not need to invest in the purchase and maintenance of physical hardware, resulting in significant cost savings. Additionally, public cloud services often provide scalability and can be accessed from anywhere with an internet connection.

The two steps that the cloud administrator should complete on I/O-intensive workloads to ensure the best performance possible are to configure the VMware Paravirtual SCSI (PVSCSI) adapter and to ensure that the VMware hardware version is 7 or later. The PVSCSI adapter provides improved performance and scalability compared to the LSI Logic Parallel SCSI controller. Additionally, the hardware version should be 7 or later to ensure that the virtual machine is able to take advantage of the latest features and enhancements. Enabling the memory hot-add feature and configuring a maximum of two CPU cores per socket will not improve the performance of I/O-intensive workloads.

Why does VMware refuse to educate their customers ... - VMware ...

VMware Technical Support Guide

Publishing Applications with VMware Horizon 7

VMware Cloud on AWS also includes a paravirtualized SCSI storage adapter, PVSCSI (also called VMware Paravirtual). The PVSCSI adapter offers a significant reduction in CPU utilization as well as potentially increased throughput compared to the default virtual storage adapters, and is thus the best choice for environments with very I/O-intensive guest applications. In order to use PVSCSI, virtual machine must be using virtual hardware version 7 .or later

Compatible top of rack switches are necessary to ensure that the data center is able to support the VMware Cloud on Dell EMC or VMware Cloud on AWS Outposts deployments [1]. The switches must support 10GE and 25GE ports, as well as Layer 3 routing protocols such as OSPF and BGP.

Dedicated subnets for SDDC management network are also needed for the deployment of VMware Cloud on Dell EMC or VMware Cloud on AWS Outposts [1]. The SDDC management network will be used for communication between the VMware Cloud components and the data center, and must be isolated from the customer network.

VMware Cloud Disaster Recovery is a managed disaster recovery-as-a-service offering that is built on the latest version of VMware vSphere 7.0. It provides an on-demand cloud consumption model, allowing administrators to rapidly power-on recovered virtual machines in the cloud, assuming cloud capacity availability. Additionally, VMware Cloud Disaster Recovery delivers a recovery point objective (RPO) of no more than 30 minutes, and can accommodate for single region failure.

Publishing Applications with VMware Horizon 7

VMware Technical Support Guide

Quick-Start Tutorial for VMware Dynamic Environment Manager ...

VMware Cloud Disaster Recovery ----------------------------------------------------- * Protect your workloads running on VMware Cloud on AWS SDDC using high-frequency snapshots to achieve RPOs as low as 30 minutes. * Availability Zone Failure Handling

A private network segment is an isolated network segment that is used for disaster recovery testing. Private network segments provide a secure and isolated environment for testing, allowing administrators to test their disaster recovery plans without risking the stability of their production environment. Private network segments also provide additional security, as they are not connected to the public internet, making them less vulnerable to external attacks. [1]

[1]

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.

VMware Tanzu Kubernetes Grid is described as a comprehensive solution for operating Kubernetes-based applications in production, as well as creating, scaling and managing clusters. It provides a centralized control plane for managing the lifecycle operations of Tanzu Kubernetes clusters. (Source: )

Example B illustrates the benefit of cloud computing where an organization can manage its cloud resources by using different cloud providers that are separate and isolated from each other. This allows the organization to make use of features and services offered by different cloud providers in order to benefit from the best of different services.

Example C illustrates the benefit of cloud computing where a business can store infrequently accessed data in the cloud in order to benefit from reduced on-premises storage costs, as cloud storage is usually cheaper than on-premise storage.

Example E illustrates the benefit of cloud computing where a developer can code an application in a cloud-based environment, and, with a few simple commands, deploy the application on the business website. This eliminates the need for the developer to set up and manage the application on their own, as the cloud platform handles the deployment and hosting of the application.

Example F illustrates the benefit of cloud computing where a large amount of storage can be made available in seconds using a cloud option. This is useful for businesses that require a large amount of storage but don't have the resources to set up and manage their own storage solution.

For more information on the benefits of cloud computing, see the VMware official documentation at