ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

Exam AWS Certified Solutions Architect - Associate SAA-C02 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C02 exam
Go to Exam

Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 271 discussion

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C02
Question #: 271
Topic #: 1
[All AWS Certified Solutions Architect - Associate SAA-C02 Questions]

Management has decided to deploy all AWS VPCs with IPv6 enabled. After some time, a solutions architect tries to launch a new instance and receives an error stating that there is not enough IP address space available in the subnet.
What should the solutions architect do to fix this?

  • A. Check to make sure that only IPv6 was used during the VPC creation.
  • B. Create a new IPv4 subnet with a larger range, and then launch the instance.
  • C. Create a new IPv6-only subnet with a large range, and then launch the instance.
  • D. Disable the IPv4 subnet and migrate all instances to IPv6 only. Once that is complete, launch the instance.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️
by sctmp at Nov. 3, 2020, 3:48 a.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

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
DarthYoda
Highly Voted 3 years, 7 months ago
cannot be A, C & D as "You cannot disable IPv4 support for your VPC and subnets; this is the default IP addressing system for Amazon VPC and Amazon EC2." in no way can you just use IPv6 So the answer is B
upvoted 66 times
someoneSays
3 years, 6 months ago
yes indeed, https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html
upvoted 3 times
...
...
sctmp
Highly Voted 3 years, 7 months ago
This one is tricky. A. How can this fix the issue? B. This could work. C. This won't work since it's saying, only subnet with IPv6 since you can't disable IPv4. D. You can't disable IPv4 cidr. I'm going for B, any inputs?
upvoted 33 times
wannaaws
3 years, 7 months ago
General idea is either remove existing ones or create a larger subnet.. so C sounds alright.
upvoted 1 times
dzenadcu
3 years, 7 months ago
B is wrong because Management decided that IPv6 is the way to go. Creating an IPv4 subnet is therefore against the requirement. I'd go with C.
upvoted 3 times
BesQpin
3 years, 6 months ago
You still need IPv4 addresses available for your hosts in your subnet, even if you intend to only use IPv6
upvoted 2 times
...
...
...
Ekie
2 years, 5 months ago
actually you can: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/#:~:text=Today%2C%20we%20take%20a%20monumental,Nitro%20System%20in%20these%20subnets. question to create subnet not VPC
upvoted 1 times
...
Sharan_25_v
3 years, 4 months ago
Actually only IPV6 option is available when creating subnets
upvoted 2 times
...
Kurp
3 years, 6 months ago
The smallest subnet size you can create with IPv6 is /64. Even if your name is Jeff Bezos, you won't have that many servers in your VPC. https://docs.aws.amazon.com/vpc/latest/userguide/get-started-ipv6.html "Creates a subnet with an /24 IPv4 CIDR block and a /64 IPv6 CIDR block in the VPC. The size of the IPv6 CIDR block is fixed (/64)."
upvoted 13 times
...
Load full discussion...
...
BECAUSE
Most Recent 1 year, 11 months ago
Selected Answer: B
B is the answer
upvoted 1 times
...
Balaganesh
2 years, 4 months ago
Selected Answer: C
https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/
upvoted 1 times
...
Six_Fingered_Jose
2 years, 6 months ago
Selected Answer: B
since you cant disable IPv4 in VPC or EC2, B seems to be the only logical solution and most likely what caused the problem in the first place. hate these trick questions with vague explanations..
upvoted 1 times
...
rude7
2 years, 8 months ago
Selected Answer: B
Answer: B Covered in Udemy course as a hands-on lab scenario
upvoted 1 times
...
cloud_collector
2 years, 9 months ago
You cannot disable IPv4 support for your VPC and subnets; this is the default IP addressing system for Amazon VPC and Amazon EC2. https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html If you create an IPv6-only subnet, be aware of the following. An EC2 instance launched in an IPv6-only subnet receives an IPv6 address but not an IPv4 address. Any instances that you launch into an IPv6-only subnet must be instances built on the Nitro System https://docs.aws.amazon.com/vpc/latest/userguide/working-with-subnets.html#create-subnets
upvoted 1 times
cloud_collector
2 years, 9 months ago
B is better
upvoted 1 times
...
...
naveenagurjara
2 years, 10 months ago
Selected Answer: B
For those who are not aware... get this.. AWS does not support IPv6 Only subnets. Even if you plan to use only IPv6, you still have to have IPv4 subnets and if you are not able to add more IPv4 ips then the IPv6 also will fail.. that's pretty dumb on AWS part...to create full dependency on IPv4...for IPv6
upvoted 3 times
Ekie
2 years, 6 months ago
actually it does: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/#:~:text=You%20can%20create%20a%20IPv6,shown%20in%20Figure%201%20below.
upvoted 1 times
...
...
arikundu
2 years, 11 months ago
Selected Answer: C
https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/
upvoted 2 times
...
GBAU
2 years, 11 months ago
Selected Answer: B
Every instance that is launched in a dual-stack VPC has IPv4 addresses and IPv6 addresses. When the IPv4 addresses are used up, instances will return the error that there are not enough IP addresses in the subnet. This solution adds additional IPv4 addresses to solve the problem. For more information about IP addresses, see IP Addressing in your VPC. For more information about IPv6, see Get started with IPv6 for Amazon VPC.
upvoted 2 times
...
kitkwok
3 years, 1 month ago
Introducing IPv6-only subnets and EC2 instances on 23 NOV 2021 https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/ Maybe C is correct after 23 NOV 2021.
upvoted 2 times
...
shirokame
3 years, 2 months ago
Should be C, please refer to the latest doc: https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet
upvoted 2 times
...
caicaizi
3 years, 2 months ago
https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html#AddaSubnet IPv6-only: Specify if this subnet should be an IPv6-only subnet. This option is only available if the subnet is in a VPC with an IPv6 CIDR block assigned. If you choose this option, you will not define an IPv4 CIDR block range for the subnet. Any EC2 instances launched in this subnet will given an IPv6 address only, not an IPv4 address. To launch an EC2 instance into an IPv6-only subnet, you must use EC2 instances built on the Nitro System. So answer is C
upvoted 3 times
...
tc15
3 years, 3 months ago
(Blog date 1 Apr 2021) Identifies; "Enable private access to Amazon Redshift from your client applications in another VPC https://aws.amazon.com/blogs/big-data/enable-private-access-to-amazon-redshift-from-your-client-applications-in-another-vpc/ No Answer fits this scenario.
upvoted 1 times
...
tc15
3 years, 3 months ago
Correct Answer: C Previously the answer would have been B but, since Jun 21, according to this blog, the restriction on creating an IPV6 only subnet was lifted. https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-ipv6-only-subnets-and-ec2-instances/ "Introducing IPv6-only subnets and EC2 instances by Rohit Aswani and Aditya Santhanam ... In June 2021, we announced our continued commitment and innovation towards the enablement of IPv6 on AWS. Today, we take a monumental step forward with the ability to create an IPv6-only architecture on AWS. With this launch, Amazon Virtual Private Cloud (VPC) now allows you to create IPv6-only subnets in your dual-stack VPCs and launch EC2 instances built on the Nitro System in these subnets."
upvoted 6 times
...
NVH
3 years, 3 months ago
According to this https://docs.aws.amazon.com/vpc/latest/userguide/vpc-migrate-ipv6.html you can enable IPv6 and run the VPC in dual-stack, so I go with C
upvoted 2 times
...
FF11
3 years, 3 months ago
Selected Answer: B
Ok i will go with B.
upvoted 1 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago