Which two steps should an administrator take to allow HTTPS access to a specific virtual machine (VM) through the public Internet for VMware Cloud on AWS? (Choose two.)
Which two steps should an administrator take to allow HTTPS access to a specific virtual machine (VM) through the public Internet for VMware Cloud on AWS? (Choose two.)
To allow HTTPS access to a specific virtual machine (VM) through the public Internet for VMware Cloud on AWS, two critical steps are necessary. First, requesting a public IP address in the VMware Cloud console is essential to enable external access (public access) to the VM. Second, configuring a DNAT rule translating the public IP address to the internal IP address of the VM ensures that incoming traffic on the public IP is properly routed to the correct internal VM. HTTPS is already a defined service, so there is no need to create a custom service for it.
I believe the correct answer is DE. HTTPS is already defined as a service, and there is no need to create a customized service for it. https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-0E34C56D-C49C-49B6-A9CF-FBFAF14A126C.html
https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-DD72B243-1D08-4B6F-8A73-A745E8B0DC81.html
correct answer is DE. HTTPS is already defined as a service, and there is no need to create a customized service for it. Public IP and DNAT are needed
I think D & E is correct
D. Request a public IP address in the VMware Cloud console. This step is necessary to obtain a public IP address that can be used for external access to the VM. E. Configure a DNAT rule translating a public IP address to an internal IP address. This step is required to map the public IP address to the internal IP address of the VM, allowing external traffic to reach the VM.
HTTPS is an existing service, so only D&E make sense
I think A & E are correct. Requesting a public IP address through the VMware Cloud console is not directly related to allowing HTTPS access to a specific VM