A cloud administrator with an existing virtual private cloud (VPC) needs to create a dedicated connection to VMware Cloud on AWS.
Which connection type would meet this requirement?
A cloud administrator with an existing virtual private cloud (VPC) needs to create a dedicated connection to VMware Cloud on AWS.
Which connection type would meet this requirement?
To create a dedicated connection to VMware Cloud on AWS from an existing virtual private cloud (VPC), the appropriate connection type would be a Private Virtual Interface. This type of connection provides a private dedicated link to AWS services, which aligns with the need for a dedicated connection to a specific cloud service like VMware Cloud on AWS.
Answer is C - Transit Virtual Interface (Transit VIF) This interface type is associated with an AWS Direct Connect Gateway that’s attached to a VMware Transit Connect. VMware Transit Connect is a managed AWS Transit Gateway that acts as a distributed router to route traffic from on-premises to SDDC Groups, between SDDCs and Amazon VPCs in the cloud. This virtual interface type allows customers to advertise their on-premises networks, as well as ESXi management and vMotion networks to the SDDC from on-premises. https://aws.amazon.com/blogs/apn/aws-direct-connect-integration-with-vmware-cloud-on-aws/
AI thinks it is "AWS Direct Connect". BUT! "However, within AWS Direct Connect, to establish a connection to a VMware Cloud on AWS environment, you would typically create a Private Virtual Interface (VIF). So, while "AWS Direct Connect" is the overarching service, "Private virtual interface" is the specific type of connection used to connect to VMware Cloud on AWS through AWS Direct Connect." The question was about "Specific connection type". which is "D" then.
Have read that question few times and here are most important words: "existing VPC" and "dedicated connection to VMC on AWS" (and not to VPC as well). Hence would go with D ("Private virtual interface") as this give dedicated access to VMC. Option C ("Transit virtual interface") gives access to VMC and VPC.
I agree with krkmar, the 2 requirements are: existing VPC and dedicated connection, which is suited for Private VIF.
The answer is C - Transit Virtual Interface (Transit VIF) This is also known as VMware Managed Transit Gateway (VTGW) in official VMware documentation: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-operations/GUID-C957DBA7-16F5-412B-BB72-15B49B714723.html
I'm confused, the listed type of virtual interfaces are part of AWS Direct Connect, meant to connect SDDCs to on-prem DCs. AWS Direct Connect virtual interfaces https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html But one of the use cases of VMware Transit connect is SDDC to VPC: VMware Transit Connect – Simplifying Networking for VMC https://blogs.vmware.com/networkvirtualization/2020/09/vmware-transit-connect-simplifying-networking-for-vmc.html/
To establish an AWS DX connection, you must create a virtual interface (VIF). A VIF can be private or public. Private and public VIFs establish private dedicated connections to the AWS backbone. Private VIF Connects to existing AWS VPCs.
Where does the question say that the "existing VPC" is on AWS?
If there is an existing VPC you would use the transit gateway to connect to it
Not the best worded questions, but I would say C. A, B, and D all relate to DX which won't help connect a SDDC to a VPC as they are both in AWS
D is correct. One of the main feature for Private VIF is that connect to exsiting AWS VPCs.
Where does the question say that the "existing VPC" is on AWS?
C is correct
I'd say A, the Public Virtual interface, based on where connection lands in this docs: https://aws.amazon.com/blogs/apn/connectivity-options-for-vmware-cloud-on-aws-software-defined-data-centers/