Which of the following are characteristics of Amazon VPC subnets?
Choose 2 answers
A.
Each subnet maps to a single Availability Zone
B.
A CIDR block mask of /25 is the smallest range supported
C.
Instances in a private subnet can communicate with the internet only if they have an Elastic IP.
D.
By default, all subnets can route between each other, whether they are private or public
E.
V Each subnet spans at least 2 Availability zones to provide a high-availability environment
answer is A and D
3
0
C is also correct
0
4
As if u create a new subnet it has route to the IG, if u only attach a EIP it can route traffic to internet.
3 correct ans for this question
A C D
0
1
Hi, correct answers are A & D
– B is wrong: /28 is the smallest
– C is wrong: private subnet should go via NAT (EIP only in public subnet)
– E is wrong: subnet can only map to ONE AZ (not span multiple)
Regards,
Frank
14
0
Perfect
1
0
No C is correct ,
U urself make a subnet public or private by attaching route to IG , bu default the route is added for IG , hence u only require an EIP.
and then u can connect.
A C D are correct
0
2
The correct answer is A & D.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html
You can create a VPC that spans multiple Availability Zones. For more information, see Creating a VPC. After creating a VPC, you can add one or more subnets in each Availability Zone. Each subnet must reside entirely within one Availability Zone and cannot span zones. Availability Zones are distinct locations that are engineered to be isolated from failures in other Availability Zones. By launching instances in separate Availability Zones, you can protect your applications from the failure of a single location. AWS assigns a unique ID to each subnet.
1
0
C, and D are wrong. A private subnet cannot reach the internet because it doesn’t have access an Internet Gateway through a NAT. An elastic IP will make no difference without those. Also subnets can never span multiple availability zones. VPC’s however, can. Only possible answers are A and D. D is correct only if proper security groups are in place.
0
0
No C is correct ,
U urself make a subnet public or private by attaching route to IG , bu default the route is added for IG , hence u only require an EIP.
and then u can connect.
A C D are correct
0
0
C is wrong because it refers to an instance in a private subnet. From the link provided by Bryan:
“If you want your instance in a public subnet to communicate with the Internet, it must have a public IP address or an Elastic IP address.”
0
0
A&D have my vote. A subnet is always a single AZ. Create a VPC and all subnets are implicitly associated with a route table by default.
1
0
Can someone update this do A & D?
0
0
A and D are correct. This article has the answers.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html
“Each subnet must reside entirely within one Availability Zone and cannot span zones.”
“Every subnet that you create is automatically associated with the main route table for the VPC.”
0
0
A & D
0
0
AD
0
0
A & D
0
0
AD
0
0
I think AD is correct
0
0
Correct Answer is A & D
0
0
A,D
0
0
A,D
0
0
A and D – easiest to pick
0
0
A.
Each subnet maps to a single Availability Zone
D.
By default, all subnets can route between each other, whether they are private or public
0
0