
Ultimate access to all questions.
A company securely connects resources within its VPC to a SaaS solution hosted in the AWS Cloud, utilizing AWS PrivateLink. The SaaS provider's solution is accessed through a PrivateLink endpoint behind their Network Load Balancer (NLB). After adding a new Availability Zone and subnets to the VPC, a network engineer encounters an issue deploying a new interface VPC endpoint for the SaaS solution in the new Availability Zone. What is causing this problem?
A
The CIDR block of the new subnets conflicts with the SaaS provider's CIDR block.
B
The enableDnsHostnames attribute and enableDnsSupport attribute were not configured on the new subnets in the new Availability Zone.
C
The SaaS provider does not offer the solution in the new Availability Zone and has not configured cross-zone load balancing for the NLB.
D
The new subnets are missing a route to the VPC internet gateway.