AWS-Advanced-Networking-Specialty試験無料問題集「Amazon AWS Certified Advanced Networking Specialty (ANS-C00) 認定」

A. Configure AS-Prepending on your BGP session

B. Enable route propagation on the VPC route table

C. Summarize your prefix announcement to less than 100

D. Announce a default route to the VPC over the BGP session

A. Configure the central VPC with a static route entry pointing the on-premises CIDR block to local VGWs.

B. Configure each application VPC with a static route entry pointing the on-premises CIDR block to the software VPN instances.

C. Configure IPSec tunnels from the on-premises router into the software VPN instances with dynamic routing.

D. Advertise all application VPC CIDR blocks to on-premises resources via the VGW in the central VPC.

A. Add routes to the VPC route tables that specify the Direct Connect connection

B. Advertise the same network routes over the Direct Connect connection and VPN connection

C. Set local preference BGP community tags on the on-premises router

D. Ensure the Direct Connect connection AS_PATH is longer than the VPN connection AS_PATH

A. Attach the second virtual interface to an alternative virtual private gateway.

B. Filter the public IP prefixes on the corporate network from the private virtual interface.

C. Attach the virtual private gateway to a VPC and enable route propagation.

D. Change the BGP advertisements from the corporate network to only be a default route.

A. Create one ALB for ail customers Create a listener rule that includes a Host header condition to match the hostname Add a forward action to route the request to the customer target group Use Amazon Route 53 to create an alias record for each customer-name example com hostname that points to the ALB

B. Create one ALB for each customer Configure the listener to route requests to the customer target group Configure an NGINX proxy server to manage connections to each ALB Use Amazon Route 53 to create a CNAME record for each customer-name example com hostname that points to the NGINX proxy server

C. Create one ALB for each customer Configure the listener to route requests to the customer target group Create an Amazon CloudFront distribution Add each ALB to the distribution as a custom origin Use Amazon Route 53 to create an alias for each customer-name example com hostname that points to the CloudFront distribution

D. Create one ALB for all customers Create a listener rule that includes an HTTP header condition to match the URL Add a forward action to route the request to the customer target group Use Amazon Route 53 to create an alias record for each customer-name example com hostname that points to the ALB

A. Create static routes in each VPC that point to the destination VPC with the virtual private gateway as the route target

B. Add the subnet range for the VPCs in us-west-1 and ap-southeast-2 to the route tables for both VPCs Add the Direct Connect gateway as a target

C. Establish a VPC peering connection between the VPCs in ap-southeast-2 and us-west-2 Add the subnet ranges to the routing tables

D. Configure the Direct Connect gateway to route traffic between the VPCs in ap-southeast-2 and us-west-2

A. Configure a private hosted zone for each application VPC, and create the requisite records Create a set of Amazon Route 53 Resolver inbound and outbound endpoint In an egress VPC Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver Associate the application VPC private hosted zones with the egress VPC and share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager. Configure the on premises DNS servers to forward the cloud domains to the Route 53 inbound endpoint.

B. Configure a private hosted zone for each application VPC, and create the requisite records Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPC Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver Associate the Route 53 outbound rules with the application VPCs and share the private hosted zones with the application accounts by using AWS Resource Access Manager Configure the on-premises DNS servers to forward the cloud domains to the Route 53 inbound endpoint.

C. Configure a private hosted zone for each application VPC, and create the requisite records Create a set of Amazon Route 53 Resolver inbound and outbound endpoints in an egress VPC Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver. Associate the application VPC private hosted zones with the egress VPC and share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager. Configure the on-premises DNS servers to forward the cloud domains to the Route 53 outbound endpoint.

D. Configure a public hosted zone for each application VPC and create the requisite records Create a set of Amazon Route 53 Resolver Inbound and outbound endpoints in an egress VPC. Define Route 53 Resolver rules to forward requests for the on-premises domains to the on-premises DNS resolver Associate the application VPC private hosted zones with the egress VPC and share the Route 53 Resolver rules with the application accounts by using AWS Resource Access Manager Configure the on-premises DNS servers to forward the cloud domains to the Route 53 inbound endpoints.

A. Configure an AWS Lambda@Edge function to validate that the traffic to the Application Load Balancer originates from CloudFront.

B. Configure CloudFront to use a custom header and configure an AWS WAF rule on the origin's Application Load Balancer to accept only traffic that contains that header.

C. Attach an origin access identity to the CloudFront origin that allows traffic to the origin that originates from only CloudFront.

D. Use an IP whitelist rule in AWS WAF within CloudFront to ensure that only known-client IPs are able to access the application.