
CIDR BLOCK/VPC Peering
Quiz by Robin d.
Feel free to use or edit a copy
includes Teacher and Student dashboards
Measure skillsfrom any curriculum
Measure skills
from any curriculum
Tag the questions with any skills you have. Your dashboard will track each student's mastery of each skill.
With a free account, teachers can
- edit the questions
- save a copy for later
- start a class game
- automatically assign follow-up activities based on students’ scores
- assign as homework
- share a link with colleagues
- print as a bubble sheet
4 questions
Show answers
- Q1You created a new VPC with CIDR range 10.10.0.0/16 and a new subnet with CIDR range 10.10.1.0/24. CIDR with /24 comes with 256 IP addresses. When you go to VPC console subnets and look at the newly created subnet. you can only see 251 IP addresses. You have not launched any resources in the newly created VPC. What would have caused this?The first four IP addresses and the last IP address in each subnet CIDR block are reserved by AWSNone of the above.AWS reserves 5 IP addresses for every VPC and are reserved from first subnet you create.AWS launches monitoring resources on behalf of you in new VPC when first subnet is created which will reserve 5 IP addresses from first subnet.120s
- Q2You are taking over AWS platform in your organization. You were asked to build a new application which would require a fleet of 20 EC2 instances inside a private VPC which should communicate with each other and no traffic going into the EC2 instances from internet but should be able to receive requests from all other EC2 instances inside the VPC. When you looked at existing VPC. it was created with 10.10.0.0/24 CIDR range which contains only 256 IP addresses. You noticed that all 256 IP addresses were being consumed by 8 subnets with 727 CIDR ranges. How can you change the CIDR range of the VPC?Add secondary CIDR range for the VPC.Create a new VPC, setup 20 EC2 instances in new VPC and peer with existing VPCEdit subnet CIDR ranges to /28 and free up unused IP addresses.Launch EC2 instances in different subnets and setup Network ACLs and Security Groups to allow traffic120s
- Q3You have setup two VPCs: VPC A has the address of *10.10.0.0/16" It also has a subnet with address space "10.10.1.0/24". VPC B has the address of °10.11.0.0/16" It also has a subnet with address space “10.111.0/28". You also have setup VPC peering connection between the two VPCs. What should be the respective route table entries in VPC A and VPC B?VPC B route table contains route with Destination as 10.10.1.0/24 and VPC A route table contains route with Destination as 10.11.1.0/28VPC A route table contains route with Destination as 10.11.0.0/16VPC A route table contains route with Destination as 10.10.1.0/24 and VPC B route table contains route with Destination as 10.11.1.0/28VPC B route table contains route with Destination as 10.10.0.0/16120s
- Q4Your organization had setup a VPC with CIDR range 10.10.0.0/16. There are total 100 subnets within the VPC and are being actively used by multiple application teams. An application team who is using 50 EC2 instances in subnet 10.10.55.0/24 complains there are intermittent outgoing network connection failures for around 30 random EC2 instances in a given day. How would you troubleshoot issue with minimal configuration and minimal logs written?Create a flow log for subnet 10.10.55.0/24.None of the above.Create flow log for each EC2 instance network interface one by one and troubleshoot the connection issue.Create a flow log for the VPC and filter the logs in CloudWatch log group.120s