AIF-C01 Practice Question 90: Private DNS Bedrock VPC Endpoint
AWS Certified AI Practitioner (AIF-C01) · Test 9 · question 10 of 10
AWS Lambda functions run in private subnets that have no internet gateway and no NAT device. They must call Amazon Bedrock models. A team creates an interface VPC endpoint for com.amazonaws.us-east-1.bedrock-runtime in those subnets, but the functions' requests to the default Regional hostname bedrock-runtime.us-east-1.amazonaws.com still time out. The team does not want to add any internet path. What is the most likely fix?
Show answer and explanation
Answer:
An interface endpoint powered by AWS PrivateLink lets you *"access Amazon Bedrock as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection."* However, the default Regional hostname only resolves to the private endpoint if private DNS is enabled: *"If you enable private DNS for the interface endpoint, you can make API requests to Amazon Bedrock using its default Regional DNS name."* Without it, the hostname resolves to public addresses that the subnets cannot reach, so calls time out. Enabling the private DNS name fixes this with no code changes, or the code can pass the vpce-... URL as endpoint_url (option C).
- A is wrong because it adds the internet path that the requirements forbid, and it would bypass the purpose of the private connection. - B is wrong because gateway endpoints exist only for Amazon S3 and Amazon DynamoDB. Bedrock is reached through interface endpoints. - D is wrong because the default endpoint policy allows full access to Amazon Bedrock through the endpoint. A custom policy is only needed to restrict access.