2V0-33.22 VMware Cloud Professional Questions and Answers

Kubernetes is an open-source container orchestration system that provides automated deployment, scaling, and management of containers. It can be used to set up an automated restart policy for containers in the event of a failure, ensuring that containers are automatically restarted when they fail.

VMware Stage Manager User's Guide

https://www.vmware.com/pdf/stagemanager1_Users_Guide.pdf

VMware Cloud on Dell EMC is a service that allows customers to deploy and manage VMware Cloud Foundation in their own data center, eliminating the need to buy and maintain their own hardware. This solution allows customers to reduce costs associated with maintaining their own hardware, as well as reduce capital expenditures by not needing to buy new hardware.

VMware Cloud on AWS is a fully managed service that allows customers to run their VMware-based workloads on the AWS Cloud. This solution allows customers to take advantage of the scalability and cost savings of the public cloud, while still being able to maintain regulatory compliance for their workloads.

According to VMware's official website, "VMware Cloud on AWS is an on-demand service that enables customers to run applications across vSphere-based cloud environments with access to a broad range of AWS services. Customers get the same architecture, features, and operational experience regardless of where you deploy applications – on-premises, in the cloud, or in a hybrid or multi-cloud configuration." [1]

[1] https://www.vmware.com/products/vmware-cloud-on-aws.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

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

https://blogs.vmware.com/management/2021/10/introduction-to-vmware-cloud-operating-model.html

The error message that the Cloud Administrator is receiving indicates that the cluster is not able to meet the requirements of the new virtual machine due to insufficient fault domains. The most likely cause of this is that one of the hosts is in maintenance mode. When a host is in maintenance mode, it is not available to the cluster, and thus cannot provide the necessary fault domains. To correct this issue, the Cloud Administrator should ensure that all hosts in the cluster are available and not in maintenance mode before attempting to create the new virtual machine.

https://www.nakivo.com/blog/vmware-snapshots-vsphere-how-to/#title-12

Follow these recommendations to get the best performance when using snapshots:

· Use snapshots as a temporary measure only.The presence of snapshots can have a significant impact on guest application performance, especially in a VMFS environment, for I/O intensive workloads. The guest applications fully recover performance after snapshots are deleted.

· Keep the snapshot chain length short when possible, to minimize the guest application performance impact.Performance degradation is higher as the snapshot chain length increases.

· If you need to increase the size of a virtual disk that has snapshots associated with it, you must delete the snapshots first before you can increase the virtual disk's size.

https://cloud.google.com/vmware-engine/docs/concepts-vmware-components Node Considerations

You can specify the number of hosts to add or remove to or from their cluster.

Private cloud initial setup happens in ~30 minutes.

Additional hosts can be added in ~15 minutes.

A three-node cluster is the minimum for production.

You can have up to 32 hosts per cluster.

You can have up to 64 hosts per private cloud.

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

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

Based on the given guidelines, the cloud administrator should select the Elastic DRS Baseline policy [1]. This policy is designed to scale the cluster automatically when additional resources are required, while also ensuring that application performance is not affected during the scaling operation. The Elastic DRS Baseline policy also ensures that resources are allocated efficiently and optimally [1], to minimize cost while ensuring that performance requirements are met.

For more information on the Elastic DRS Baseline policy [1], see the VMware official documentation at https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.sddc-management/GUID-FDD3A8AC-E42C-4B92-9C1D-8EB49D6C7129.html.

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

https://vcdx.vmware.com/content/dam/digitalmarketing/vmware/ru/pdf/techpaper/vmware-horizon-7-application-publishing.pdf

VMware Technical Support Guide

https://www.vmware.com/pdf/techsupportguide.pdf

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

https://techzone.vmware.com/resource/quick-start-tutorial-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 https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-disaster-recovery/GUID-067EE6DF-80CC-44D2-94E6-D7183A239D9A.html

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/rn/vmware-cloud-disaster-recovery-release-notes/index.html

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/

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: https://docs.vmware.com/en/VMware-NSX-Data-Center/2.4/nsx_24_sdn_networking/GUID-A4A6E4A8-FD7C-4B6E-A3D3-6F9B6D0578C2.html.

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

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://vmc.techzone.vmware.com/understanding-segments-vmc-aws

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

• 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

VMware Tanzu Mission Control provides a central platform to manage and view all Tanzu Kubernetes clusters and workloads running in the environment. It allows administrators to set policies across multiple clusters, set up cluster identities, monitor cluster health and performance, and much more. Tanzu Mission Control also provides access to a variety of cloud-native tools, such as Kubernetes Dashboard, Helm, and Kubeapps.

Publishing Applications with VMware Horizon 7

https://vcdx.vmware.com/content/dam/digitalmarketing/vmware/ru/pdf/techpaper/vmware-horizon-7-application-publishing.pdf

VMware Technical Support Guide

https://www.vmware.com/pdf/techsupportguide.pdf

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

https://techzone.vmware.com/resource/quick-start-tutorial-vmware-dynamic-environment-manager

"VMware Tanzu® Mission ControlTM is a centralized management platform for consistently operating, managing, and securing Kubernetes infrastructure and modern applications across teams and clouds. It provides a global view of all of the Kubernetes clusters. You can use the resource hierarchy to manage and enforce consistent policies across Kubernetes clusters. "

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

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-DFB3C048-5728-4DE9-9380-7240748875C3.html

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.

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.

Incident and Problem Management: VMware will provide incident and problem management services (e.g., detection, severity classification, recording, escalation, and return to service) pertaining to availability of the Service Offering. VMware is responsible for incident and problem management (e.g., detection, severity classification, recording, escalation, and return to service) pertaining to all virtual machines that you have deployed in your SDDC.

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/vmw-cloud-aws-service-description.pdf

This would enable the user to have the necessary permissions to deploy virtual machines - and thus, would ensure that all of the necessary virtual machines are deployed in a timely and efficient manner.

• VMware Cloud on AWS Documentation: "Deployment of virtual machines"
• VMware Cloud on AWS Documentation: "Creating virtual machines with the VMware Cloud on AWS console"
• VMware Cloud on AWS Documentation: "Managing virtual machines with the VMware Cloud on AWS console"

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

https://blogs.vmware.com/management/2022/08/forwarding-vsphere-audit-and- authentication-events-from-vrealize-log-insight-to-a-siem.html

VMware Cloud on AWS is a managed service, and VMware handles the updates and patches to the infrastructure. When VMware notifies customers of upcoming maintenance or updates, it is usually for informational purposes, so the customer is aware. Unless there's a specific action item mentioned in the notification (which would be unusual), no action is required from the customer's end.

Upgrades for VMware Cloud on AWS SDDCs are deployed in a rollout across the service. When an upgrade rollout is available for your organization, you receive an email notification and a notification in the VMware Cloud Console. Typically, you receive this notification 30 to 60 days before upgrades begin for a rollout. After you receive the notification, you can submit a scheduling request for any of your SDDCs. So respond is required for initial schedule. If you receive the notification 7 days before start, this means you already responded to the proposed date and agree on it. https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-EE89B216-BE93-4A1A-9280-8F20E2A5266F.html https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-7725CAAC-BBDB-4F80-991F-1D1ADDE12216.html#GUID-7725CAAC-BBDB-4F80-991F-1D1ADDE12216

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-1A175E91-2317-4261-A63E-B398D92ECE8D.html 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.

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