Topic 1 Question 185
A company securely connects resources that are in its VPC to a software as a service (SaaS) solution from a SaaS provider. The SaaS solution is hosted in the AWS Cloud and is powered by AWS PrivateLink. The company uses a PrivateLink endpoint to access the SaaS solution behind the SaaS provider's Network Load Balancer (NLB).
The company recently added a new Availability Zone and new subnets to its VPC. A network engineer is unable to deploy a new interface VPC endpoint for the SaaS solution in the new Availability Zone.
What is the cause of this problem?
The CIDR block of the new subnets conflicts with the SaaS provider's CIDR block.
The enableDnsHostnames attribute and enableDnsSupport attribute were not configured on the new subnets in the new Availability Zone.
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 new subnets are missing a route to the VPC internet gateway.
ユーザの投票
コメント(4)
- 正解だと思う選択肢: C👍 2rdiaz2024/06/12
- 正解だと思う選択肢: C
AWS PrivateLink endpoints require the service to be available in the Availability Zone where the endpoint is being created. If the SaaS provider does not offer the service in the new Availability Zone and cross-zone load balancing is not configured for the NLB, the endpoint cannot be deployed in that Availability Zone. This is a likely cause of the problem because the endpoint creation depends on the service being present and accessible in the desired Availability Zone.
👍 2Akshay04032024/07/23 - 正解だと思う選択肢: C
this is C
👍 1cas_tori2024/08/27
シャッフルモード