VMware Cloud on AWS Management Exam 2019 5v0-31.19 – Exam Review and Tips

VMware and Amazon Web Services are making a significant investment in providing a vSphere experience in a hyperscaler environment and we continue to see adoption for Cloud Service Providers utilizing VMware Cloud on AWS as an offering for managed services.

In this post, I will review my approach, what to expect on the exam, and my raw study notes.

I decided to prepare for the VMware Cloud on AWS Management Exam 2019 (Exam 5v0-31.19) and sit for it. While there’s a lot of great material that I will review below, I wanted to provide my approach for others.

My Approach

  • Always start with the blueprint. I print this out and go through line to verify I have a base level understanding of the objective and what I need to focus on.
  1. First off, there is some great material already online that I reviewed:
    1. Paul McSharry‘s writeup on the material and his mindmap which is here.
    2. Manny Sidhu did a great writeup of his notes and approach here.
  2. I went through the VMware Cloud on AWS: Deploy and Manage – On Demand course on VMware Education.
    1. This was beneficial as it covered a lot of the fundamentals including some AWS concepts I was not aware of.
    2. I would highly recommend this for people even new to VMware vSphere as it reviews many of these concepts at a high-level.
  • Went through the VMware Hands on Lab for VMware Cloud on AWS (1987-01-HBD) – this is great to get your hands-on and experience setting up a SDDC. Walks through many of the same concepts I saw in the Deploy and Manage course.


It’s 30 questions and is done via the Pearson Vue site online. I thought it was very fair as a skill/badge exam and goes over many of the fundamental requirements. As expected, it’s true to the blueprint.

My Raw Notes

For me, I always prepare a final checklist of things I review before I take any examination. Below is my list of raw notes I used before I took the exam. As they are my raw notes, expect some abbreviations.

Anyway, enjoy the exam and I look forward to the expansion of VMware Cloud on AWS!

VMC on AWS Study Notes:

  1. Use Cases:
    1. Extension of onprem DC to the public cloud to expand resource capacity, increase disaster avoidance and recovery options, or localize application instances.
    2. Consolidation
    3. Peering the private and public cloud that allows for application mobility
  2. Global compliance – ISO, SOC1-3, GDPR, and HIPAA
  3. Many different AWS regions available plus GovCloud
  4. SDDC
    1. Minimum of 3 hosts and maximum of 32 hosts
    2. Up to 10 clusters can be added to a SDDC
    3. Stretched Cluster – between two AZ’s (min of 6 hosts and max of 28)
  5. Host Configuration
    1. 2 18 core sockets – Broadwell 
    2. 512 gibibytes of memory (550GB)
    3. 14.3TB of NVMe SSD’s – 3.6TB for flash, 10.7TB for capacity
    4. 1 AWS ENA – 25Gbps
  6. vSAN/Storage
    1. Two Disk Groups per host
    2. Dedupe/Compression is on by default
    3. Encryption is happening at the drive level
    4. Two different datastores – WorkloadDatastore (for workloads) and vsanDatastore (management VMs, cannot be modified)
    5. Default policy is PFTT 1, RAID1
    6. Can pick from PFTT of 1 to 3, RAID1/5/6 (if available hosts)
    7. Since All Flash, reads are from cap tier
  7. Stretched Cluster
    1. Sync writes between two AZ’s
    2. Witness host is added and not charged to customer
    3. Pre-reqs
      1. Requires a AWS VPC with two subnets, one subnet per AZ
      2. Smallest SC is 6, largest is 28
      3. Must grow in pairs
      4. Adding hosts trombones between AZs – first one is added to AZ1, next is AZ2, next is AZ1, and so on
    4. Site Disaster Tolerance – default is dual site mirroring 
  8. Network
    1. Traffic is separate between management and compute gateways
    2. Amazon Direct Connect allows for low-latency connections between on-prem and AWS. 
    3. ENA’s are highly redundant even though there’s a single pNIC per host
    4. Two types of VPCs
      1. One created and managed by VMware – underlying VPC that is created when the SDDC is created 
      2. Second – VPC that you create so you can peer with native AWS services 
    5. Firewall
      1. Default deny all
      2. Must add rules for vCenter access, IPsec, etc
      3. Firewall Rule Accelerator created a group of rules to accelerate successfully connecting a VPN tunnel
    6. Logical Networks
      1. Routed network – internal communication over a IPsec or Internet connection. Normal overlay network that we are used to. 
      2. External Network – utilized for L2VPN connectivity. Requires Tunnel ID. Think of this as a subint
    7. Inter-Networking Scenarios
      1. Compute GW – IPsec for guest OS connectivity
      2. Compute CW – L2VPN for vMotion, same L2 domain 
      3. Direct Connect with pub virtual interface – in conjunction with IPsec or L2VPN or Pub Internet. Used for AWS services
      4. Direct Connect with private virtual interface – secured to direct SDDC
  9. Hybrid Linked Mode
    1. Allows for a single management interface between on-prem vCenter and VMC
    2. Pre-req for migration from on-prem to VMC
    3. Same SSO is not needed 
    4. Configuration is only done from one of the vCenters to configure HLM. Will only be visible from this vCenter for future management. So, no bi-directional UI support. 
    5. Pre-reqs
      1. IPsec VPN connection between on-prem and SDDC management gateway
      2. Network connectivity between your VMC vCenter and on-prem vCenter server and identity source
      3. Same DNS 
      4. Less than 100ms RTT
      5. Misc ports needed for successful connectivity 
    6. vCenter Cloud Gateway Appliance configured HLM. 
  10. HCX
    1. Can do migrations between vSphere 5.1 to VMC
    2. No charge
  11. VPC
    1. Only one VPC can be connected to a SDDC
    2. VPC subnets can only reside in one AZ. 
    3. Elastic IP addresses are public IPv4 addresses mapped to the AWS account, not the resource.
    4. Connecting – 
      1. Must connect a Amazon VPC or if it’s a single node SDDC, can delay up to 14 days.
  12. Migrating VMs
    1. Cluster EVC and Per-VM EVC 
      1. In 6.7, can enable disable or change the EVC mode at the VM level. 
    2. Requirements for Hybrid Cold Migration
      1. vSphere 6.5 patch d or later, 6.0U3, vSphere 5.1/5.5
      2. IPsec VPN
      3. HLM but can use move-vm cmdlet 
    3. Hybrid Migration with vMotion
      1. Minimum bandwidth of 250Mbps and less than 100ms RTT
      2. vSphere 6.5 patch d / vSphere 6.0U3
      3. IPsec VPN
      4. vCSS/vDS 6.0 or 6.5
      5. AWS DC with a private virtual interface 
      6. HLM or move-vm cmdlet 
      7. L2VPN to extend VM networks between on-prem and VMC
      8. All FW rules in order. 
      9. VM hardware version 9, Cluster based EVC baseline on Broadwell
    4. Per-VM EVC
      1. Must be hardware version 14 or greater 
      2. VM must be powered off to change Per-VM EVC
  13. Permissions and Security
    1. CloudAdmin –
      1. Necessary privileges for creating/managing workloads in the SDDC
      2. Does not allow changing the configuration of management components that are supported by VMW
    2. CloudGlobalAdmin – 
      1. Associated with global privileges that allows you to create and manage content library objects and perform other global tasks. 
    3. cloudadmin@vmc.local is the default user generated during creation. 
    4. Other users cannot be created until HLM is configured. DO NOT modify solution users associated with the VMC created in an on-prem vSphere domain
  14. Elastic DRS
    1. Allows the SDDC to scale based on resource thresholds 
    2. Not supported for multi-AZ deployment or single host SDDC
    3. If a user adds or removes a host, current EDRS remediations are ignored 
  15. Licensing/Pricing
    1. On-Demand, One-Year and Three-Year Subscription models
    2. HLP discounts of up to 25%
    3. Site Recovery is an add-on cost
    4. All other AWS services are billed separately
  16. Cloud Services Roles
    1. Organization Owners – 
      1. Can have one or more
      2. Owners can invite additional owners and users, manage access
    2. Organization Users –
      1. Access VMware Cloud services
      2. Cannot invite users, change access, or remove
  17. Deployment
    1. Default Subnet CIDR is – reservations for other RFC1918 addresses
    2. is reserved for default compute
    3. Maximum hosts are dictated by the CIDR block you state
  18. Content Libraries 
    1. Onboarding Assistant is a java CLI tool for transferring to VMC
    2. Can still utilize subscribe functionality
    3. Utilize vSphere Client to upload files
  19. Site Recovery
    1. vSphere Replication based
    2. Supports Active-Active, Active-Passive, Bidirectional
    3. Pre-Reqs
      1. vCenter 6.7/6.5/6.0U3, ESXi 6.0U3 or later
      2. SRM 8.x on-prem

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: