A cloud administrator establishes a VPN connection to the VMware Cloud data center but Is unable to access the VMware Cloud vCenter. Which step can the administrator take to resolve this?
Correct Answer:
D
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-ED8B8 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.
A cloud administrator would like the VMware Cloud on AWS cluster to automatically scale-out and scale-In based on resource demand. Which two Elastic DRS policies can be configured to meet this requirement? (Choose two.)
Correct Answer:
DE
The two Elastic DRS policies that can be configured to meet the requirement of automatically scaling out and in based on resource demand are the Custom Elastic DRS policy and the Optimize for Rapid Scale-Out policy. The Custom Elastic DRS policy allows you to configure the cluster to scale out when certain resource utilization thresholds are met, while the Optimize for Rapid Scale-Out policy allows you to configure the cluster to scale out when resource utilization is high and scale in when utilization is low.
Elastic DRS is a feature of VMware Cloud on AWS that enables automatic scaling of the cluster based on resource demand. To meet the requirement of automatic scaling, the administrator can configure a custom Elastic DRS policy or the Optimize for Rapid Scale-Out policy. Custom Elastic DRS policy allows administrator to define the custom rules for scale-out and scale-in based on resource utilization thresholds. Optimize for Rapid Scale-Out policy automatically scales-out the cluster when resource utilization threshold is met.
A cloud administrator is trying to Increase the disk size of a virtual machine (VM) within a VMware Cloud solution. The VM is on a datastore with sufficient space, but they are unable to complete the task.
Which file is preventing the administrator from completing this task?
Correct Answer:
C
The .vmdk file contains the virtual machine's hard disk configuration and is preventing the administrator from increasing the disk size. The .vmdk file must be edited to allow the administrator to increase the disk size. More specifically, the administrator must edit the descriptor file within the .vmdk file to change the capacity of the disk.
A cloud administrator wants to migrate a virtual machine using VMware vSphere vMotlon from their
on-premises data center to their VMware Cloud on AWS software-defined data center (SDDC), using an existing private line to the cloud SDDC.
Which two requirements must be met before the migration can occur? (Choose two.)
Correct Answer:
CD
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-1A175 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 Require 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 centerwith 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.
Which VMware technology 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? (Select one option)
Correct Answer:
B
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.