Answer-first summary for fast verification
Answer: The SaaS provider does not offer the solution in the new Availability Zone and has not configured cross-zone load balancing for the NLB.
The issue described involves the inability to deploy a new interface VPC endpoint for a SaaS solution in a newly added Availability Zone within a VPC. The key detail here is that the SaaS solution is accessed via AWS PrivateLink, which requires specific configurations to function correctly. Option A is incorrect because a CIDR block conflict would typically prevent the creation of the subnets themselves, not just the deployment of a VPC endpoint. Option B is incorrect because the enableDnsHostnames and enableDnsSupport attributes are related to DNS resolution within the VPC and do not directly impact the ability to create a VPC endpoint. Option D is incorrect because a route to the VPC internet gateway is not required for PrivateLink connections, which are private and do not traverse the internet. Option C is correct because AWS PrivateLink requires that the service (in this case, the SaaS solution) is available in the Availability Zone where the endpoint is being created. If the SaaS provider has not extended their service to the new Availability Zone or has not configured their NLB for cross-zone load balancing, the endpoint cannot be created in that zone.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
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.