Podcast
Questions and Answers
When attaching a VPC to a transit gateway, how many subnets can you specify for each enabled Availability Zone?
When attaching a VPC to a transit gateway, how many subnets can you specify for each enabled Availability Zone?
- Two subnets for each Availability Zone
- Multiple subnets for each Availability Zone
- No subnets are specified for each Availability Zone
- One subnet for each Availability Zone (correct)
What happens when you enable an Availability Zone for a transit gateway attachment?
What happens when you enable an Availability Zone for a transit gateway attachment?
- A network interface is placed in the specified subnet using one IP address from the subnet (correct)
- The transit gateway places multiple network interfaces in the specified subnet
- Traffic is routed only to the specified subnet within the VPC
- The transit gateway charges additional fees for cross-Availability Zone traffic
What happens if traffic is sourced from an Availability Zone where the destination attachment is not present?
What happens if traffic is sourced from an Availability Zone where the destination attachment is not present?
- The traffic is rerouted to a specific predefined Availability Zone
- The transit gateway charges extra fees for routing that traffic
- The traffic is dropped and does not reach the transit gateway
- AWS Transit Gateway internally routes that traffic to a random Availability Zone with the attachment present (correct)
What is recommended to ensure availability when attaching a VPC to a transit gateway?
What is recommended to ensure availability when attaching a VPC to a transit gateway?
When can you enable appliance mode support for a VPC attachment in a transit gateway?
When can you enable appliance mode support for a VPC attachment in a transit gateway?