Exam AWS Certified Advanced Networking - Specialty ANS-C01 All Questions

View all questions & answers for the AWS Certified Advanced Networking - Specialty ANS-C01 exam

Exam AWS Certified Advanced Networking - Specialty ANS-C01 topic 1 question 93 discussion

Exam question from Amazon's AWS Certified Advanced Networking - Specialty ANS-C01

Question #: 93
Topic #: 1

[All AWS Certified Advanced Networking - Specialty ANS-C01 Questions]

A company's application team is unable to launch new resources into its VPC. A network engineer discovers that the VPC has run out of usable IP addresses. The VPC CIDR block is 172.16.0.0/16.

Which additional CIDR block can the network engineer attach to the VPC?

A. 172.17.0.0/29
B. 10.0.0.0/16
C. 172.17.0.0/16
D. 192.168.0.0/16

Show Suggested Answer

Suggested Answer: C 🗳️

by takecoffe at June 6, 2023, 2:03 p.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

albertkr

Highly Voted 2 years ago

Selected Answer: C

option A prefix length is too long (/29) option B and D cannot be associated with CIDR block from range 172.16.0.0/12 due to cidr block restrictions. it leaves option C as the feasible option.

upvoted 12 times

...

49ca6f2

Most Recent 5 months, 1 week ago

Selected Answer: B

This question has two correct answers : B and D. You can only add non overlapping CIDR as additional cidr.

upvoted 1 times

...

Spaurito

7 months, 3 weeks ago

B is the correct answer. If you're adding a CIDR Block to the VPC you can't have overlap with the existing VPC CIDR. C would overlap adding that block and actually can't be done as mentioned by evargasbrz. The correct answer is B

upvoted 1 times

...

Ravan

10 months, 1 week ago

Selected Answer: C

C. 172.17.0.0/16 Explanation: The current VPC has a CIDR block of 172.16.0.0/16, which falls within the 172.16.0.0/12 range. According to AWS documentation, you can add additional CIDR blocks from the 172.16.0.0/12 range (which includes 172.16.0.0/16 to 172.31.0.0/16), provided they do not overlap with the existing CIDR block. 172.17.0.0/16 is a valid CIDR block within the 172.16.0.0/12 range, and it does not overlap with the existing 172.16.0.0/16 CIDR block. Option A (172.17.0.0/29) and Option B (10.0.0.0/16) are also valid CIDR blocks, but the /29 block would provide too few IP addresses, and Option B is from a different RFC 1918 range, which is not the most straightforward choice for expanding within the same address space.

upvoted 3 times

...

Marfee400704

1 year, 4 months ago

I think that it's correct answer is C according to SPOTO products.

upvoted 1 times

...

evargasbrz

1 year, 10 months ago

Selected Answer: B

B -> is the right answer here. Guys, you are not able to add any one of the following CIDRs A. 172.17.0.0/29 C. 172.17.0.0/16 D. 192.168.0.0/16

upvoted 1 times

shinzor

1 year, 7 months ago

You can't associate a different CIDR range if you already use a block from 172.16.0.0/12 (which includes A and C, so for sure not B and D. However A is way too less IP addresses, so only viable option would be C

upvoted 1 times

...

[Removed]

1 year, 11 months ago

Selected Answer: C

Option C

upvoted 1 times

...

demoras

2 years ago

Selected Answer: C

The correct answer is C

upvoted 2 times

...

demoras

2 years ago

The correct answer is C

upvoted 2 times

...

Ayptek

2 years ago

Selected Answer: C

The correct answer is C

upvoted 2 times

...

takecoffe

2 years ago

Selected Answer: C

https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html#add-cidr-block-restrictions Only it will also us to add 172.17.0.0/16

upvoted 2 times

Training

2 years ago

Important Some AWS services use the 172.17.0.0/16 CIDR range. To avoid future conflicts, don’t use this range when creating your VPC. For example, services like AWS Cloud9 or Amazon SageMaker can experience IP address conflicts if the 172.17.0.0/16 IP address range is already in use anywhere in your network. For more information, see Can't connect to EC2 environment because VPC's IP addresses are used by Docker in the AWS Cloud9 User Guide.

upvoted 5 times

[Removed]

1 year, 8 months ago

It's tricky but if you read through the article only 172.17.0.0/16 is not restristed. There's no option to add 10.0/8 and 192.16./16 subnet

upvoted 1 times

...

JosMo

1 year, 11 months ago

https://docs.aws.amazon.com/cloud9/latest/user-guide/troubleshooting.html#docker-bridge

upvoted 1 times

...