2V0-33.22 VMware Cloud Professional Questions and Answers

RAID-1 is a mirror configuration that provides high availability by creating multiple copies of a VMDK. RAID-5 and RAID-6 are erasure coding configurations that provide fault tolerance by distributing data and parity across multiple hosts.

The number of failures to tolerate (FTT) determines how many copies or parity blocks are created for each VMDK. For example, RAID-1 FTT = 2 means that there are three copies of each VMDK.

Therefore, based on your requirements, a possible VM storage policy setting could be RAID-1 FTT = 2, which would provide redundancy at the highest level possible with six hosts.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html

Route-based IPSec VPNs provide the flexibility to dynamically learn when new networks are created, making them the ideal choice for establishing connectivity between an on-premises data center and VMware Cloud. Route-based IPSec VPNs use the Border Gateway Protocol (BGP) to dynamically learn and propagate routes over the VPN tunnel, allowing for scalable and secure connectivity. [1]

[1] https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-EDA5A6E5-6C5B-4F66-9C2F-2C6D4F6EF8F6.html

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

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.

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.

https://blogs.vmware.com/virtualblocks/2021/09/28/operational-air-gaps/

Operational isolation (operational “air-gapping”) is critical to DR. VMware Cloud DR was designed from the very beginning for its systems and repository to be operationally isolated and for instantiating isolated recovery environments.

https://vmc.techzone.vmware.com/understanding-segments-vmc-aws

Tanzu Kubernetes clusters can be deployed in a VMware Cloud environment using the VMware Cloud Console. The VMware Cloud Console provides a user-friendly interface that allows users to quickly deploy and manage Tanzu Kubernetes clusters. The standard open-source kubectl can also be used to deploy Tanzu Kubernetes clusters. However, this requires a more in-depth knowledge of the kubectl command-line interface. Additionally, users can use the vSphere Plugin for kubectl to deploy and manage Tanzu Kubernetes clusters. This plugin provides a graphical user interface to manage the clusters, as well as additional features such as the ability to make cluster-level changes

https://docs.vmware.com/en/VMware-Tanzu-for-Kubernetes-Operations/1.4/tko-reference-architecture/GUID-deployment-guides-tanzu-standard-on-vmc-aws.html

Managing Costs:

With its capacity and cost management features, vRealize Operations Cloud can predict future demand and provide actionable recommendations to help in managing costs.

Reclamation of Existing Resources:

Assess workload status and resource contention in data centers across your environment:

• Determine the time remaining until CPU, memory, or storage resources run out.
• Realize cost savings when underutilized VMs are identified and reclaimed to be deployed more effectively.

Future Infrastructure Requirements

Run what-if scenarios:

• Identify how much capacity remains after you add or remove VMs or hosts.
• Add hyperconverged infrastructure (HCI) nodes.
• Get a recommendation based on the cost relative to workload placement on different hosts, clusters, data centers, and even different clouds.

Cloud Migration Planning:

Migration planning shows you the capacity and cost information after the migration to a cloud-based infrastructure.

Cost Overview

vRealize Operations Cloud supports costing for private clouds, public clouds, and VMware Cloud infrastructure.

You can track expenses for a single virtual machine, and identify how these expenses attribute to the overall cost associated with your private cloud accounts and VMware Cloud infrastructure accounts.

On the Cost Overview home page in vRealize Operations Cloud, you can find details about the costs associated with your VMware Cloud infrastructure accounts, public cloud accounts, and your private cloud accounts.

You can view the Total Cost of Ownership, Potential Savings, and Realized Savings for your VMware Cloud infrastructure cloud accounts and vSphere private cloud accounts, and Total Cost of Ownership for your private cloud accounts.

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

https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.6/air-gap-reference-architecture/GUID-deployment-guides-tkg-vsphere-vds-airgap.html

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

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

https://docs.vmware.com/en/VMware-Workspace-ONE-Access/20.10/workspace_one_access_install/GUID-E81B6B1B-A3D1-40D0-806A-3D31502C53A5.html

The Cloud Services Portal communicates with the Workspace ONE Access Connector via port 443 (HTTPS). According to the VMware documentation [1], the Cloud Services Portal connects to the Access Connector on port 443 to authenticate users and authorize access to the cloud service. The Access Connector listens on port 443 and communicates with the Active Directory using LDAP over TLS (LDAPS) on port 636. Reference: https://docs.vmware.com/en/VMware-Workspace-ONE-Access/services/com.vmware.access.admin.configure.doc/GUID-F5C6FD9E-36DA-4B1F-A7E7-CF8F64A81D78.html

Tanzu Kubernetes Grid is a service from VMware Cloud that enables customers to deploy and manage Kubernetes applications in the cloud. In order to deploy a namespace or their Kubernetes Application developments, an administrator must configure a Tanzu Kubernetes Cluster and a Management Cluster.

A Tanzu Kubernetes Cluster is a cluster of nodes that are used to run applications and services. The nodes are connected to the Management Cluster, where administrators can manage and monitor deployments.

The Management Cluster is a cluster of nodes that are used to manage and monitor the Tanzu Kubernetes Cluster nodes. It provides the tools to manage and monitor deployments, as well as to configure and maintain the Tanzu Kubernetes Cluster nodes.

According to VMware's official website, "Tanzu Kubernetes Grid is a service that provides a simplified way to deploy and manage Kubernetes applications in the cloud. It provides a single control plane for managing multiple Kubernetes clusters, allowing customers to easily deploy and manage their applications across multiple clusters and environments." [1]

[1] https://www.vmware.com/products/tanzu-kubernetes-grid.html

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.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-961C4B32-6093-4C2E-AFE5-5B1F56BF4EEE.html

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-961C4B32-6093-4C2E-AFE5-5B1F56BF4EEE.html#:~:text=In%20a%20new%20SDDC%2C%20Elastic,AWS%20Availability%20Zone%20failure%20occurs .

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 Dell EMC: https://www.vmware.com/products/vmware-cloud-on-dellemc.html And the official VMware documentation on VMware Cloud on AWS Outposts: https://www.vmware.com/products/vmware-cloud-on-aws-outposts.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.

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.

The best option to meet the requirements of quickly migrating 1,000 VMs with the lowest latency and most reliable connection possible is to use AWS Direct Connect. AWS Direct Connect provides a dedicated network connection between an on-premises data center and the Amazon Web Services (AWS) cloud, allowing for the transfer of data across the two locations. It is more reliable and has lower latency than other options such as Layer 2 VPN, VMware Transit Connect, and IPsec VPN. Additionally, AWS Direct Connect provides the highest performance and throughput of any of the on-premises data center connectivity options.

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

https://communities.vmware.com/t5/VMware-Education-Services/Why-does-VMware-refuse-to-educate-their-customers/td-p/2005973

VMware Technical Support Guide

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

Publishing Applications with VMware Horizon 7

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

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

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/

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.

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

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.

https://docs.vmware.com/en/VMware-Cloud-Disaster-Recovery/services/vmware-cloud-dr-security-best-practices/GUID-BCC03463-437B-4DBE-BE21-0D43D5BA5776.html

A cloud administrator requires an external secure connection into their data center to use Border Gateway Protocol (BGP). The best connection type to use for this purpose is a Route-based virtual private network (VPN). This type of VPN is secure, as it uses encryption and authentication to protect the data transmitted over the connection. Additionally, it allows for the configuration of BGP to ensure that the data traffic is routed to the desired destination.

PREPARING FOR VMWARE CLOUD ON AWS

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vmc-aws/preparing-for-vmware-cloud-on-aws.pdf

Publishing Applications with VMware Horizon 7

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

What is Network Virtualization? | VMware Glossary

https://www.vmware.com/topics/glossary/content/network-virtualization.html

https://aws.amazon.com/es/blogs/apn/connectivity-options-for-vmware-cloud-on-aws-software-defined-data-centers/

The two use cases that apply to NSX logical routing are A. You must provide external connectivity to VMs and containers, and B. Your organization must provide connectivity between VMs and containers that are connected to different segments. NSX logical routing allows you to provide external connectivity to VMs and containers, and to provide layer 3 connectivity between VMs and containers that are connected to different segments. It does not provide layer 2 connectivity between VMs and microservices or intrinsic security for VMs connected to different segments.

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.

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.

When a VPN is established between the data center and the SDDC Instance, it allows the organization to create a private and secure connection between their on-premises infrastructure and their workloads running in the cloud. By advertising a 0.0.0.0/0 route, the organization is essentially routing all traffic to the VPN tunnel, which means that all traffic including traffic destined for the data center and internet traffic, will be sent through the VPN tunnel to the company's data center.

It is important to note that this configuration depends on the company's network architecture and security policies, and that there may be other alternatives that better fit the organization's needs.

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 AWS Gateways: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.networking/GUID-1F2D1BFC-F5C7-4534-8B49-39F9D08E7F1A.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.