MENU
A Network Engineer is provisioning a subnet for a load balancer that will sit in front of a fleet of application servers in a private subnet. There is limited IP space left in the VPC CIDR. The application has few users now but is expected to grow quickly to millions of users.
What design will use the LEAST amount of IP space, while allowing for this growth?
Suggested Answer: C
Get Premium ANS-C01 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
BR
Brett
11 months ago
Definitely disagree with using /29, we need more flexibility!
TE
Telma
11 months ago
Two /28 subnets would be overkill for now, though.
WY
Wynell
11 months ago
Surprised they even considered /29 for a load balancer. Seems risky!
EV
Evangelina
11 months ago
I think option B is the best choice for future-proofing!
NI
Nickolas
12 months ago
A /29 subnet only gives you 6 usable IPs, not enough for growth.
MA
Mayra
12 months ago
Adding another VPC CIDR sounds like a workaround, but I wonder if it complicates the design too much. I’m leaning towards the /28 option.
TI
Tijuana
1 year ago
I think I saw a similar question where using a /28 subnet was recommended for load balancers. It seems like it might provide more flexibility.
KE
Kendra
1 year ago
I feel like using two /29s could be a good option for redundancy, but I'm not sure if it's the most efficient use of IP space.
LA
Laquanda
1 year ago
I remember studying subnetting, and I think a /29 subnet only gives us 6 usable IPs, which might not be enough for future growth.
MA
Mari
1 year ago
I think option B might be the best choice here. Using a single /29 subnet for the Network Load Balancer and then adding another VPC CIDR for future growth seems like a smart way to optimize the IP space.
KR
Kris
1 year ago
I'm not sure about this one. The question is asking for the design that uses the least IP space, but it also needs to allow for growth to millions of users. I'll have to weigh the tradeoffs.
HU
Hubert
1 year ago
Hmm, this is a tricky one. I'll need to think through the IP space requirements and load balancer options carefully.
CY
Cyndy
1 year ago
Okay, let's see. We need to use the least amount of IP space while allowing for future growth. I'm leaning towards option B or D.
CA
Cassi
1 year ago
Hmm, I'm a bit unsure about this one. I know we need to ensure we can view all the resources, but I'm not sure which of these options is the right approach.
CH
Chantay
2 years ago
Option C all the way! Two /28 subnets for the Network Load Balancer is the clear winner here. I mean, who needs a ton of IP space when you can just 'network' your way through the problem? *wink wink*
MA
Maryann
2 years ago
Exactly, no need to waste IP space when you can plan smartly for the future.
SY
Sylvie
2 years ago
Definitely, it's all about optimizing the IP space while planning for scalability.
MA
Matt
2 years ago
Agreed! Using two /28 subnets for the Network Load Balancer makes the most sense.
DE
Deandrea
2 years ago
I think option C is the best choice too. It's efficient and allows for future growth.
JA
Janine
2 years ago
Hmm, this is a tough one. I'm torn between options C and D. Both seem like viable solutions, but I'm leaning towards C since the /28 subnets will give us more flexibility in the long run. Although, I do have to admit, the idea of an 'Application Load Balancer' working out its gains at the gym is pretty amusing.
HO
Holley
2 years ago
I'd go with option B. A single /29 subnet for the Network Load Balancer now, and adding a new VPC CIDR later for future growth seems like a prudent and efficient approach. Plus, who doesn't love a good 'Network Load Balancer' pun?
FL
Florinda
2 years ago
Definitely, it's a practical solution that will scale well as the application grows.
MA
Maybelle
2 years ago
Agreed, using one /29 subnet for the Network Load Balancer now and adding another VPC CIDR later is a smart move.
VE
Venita
2 years ago
I think option B is the way to go. It allows for future growth without wasting too much IP space.
DE
Devorah
2 years ago
I see your point, Moon. But I think option C is the most efficient with two /28 subnets for a Network Load Balancer in different Availability Zones.
MO
Moon
2 years ago
I disagree, I believe option B is better as it allows for future growth by adding another VPC CIDR.
JA
Jaclyn
2 years ago
Hmm, option C looks like the way to go. Two /28 subnets for the Network Load Balancer should give us plenty of room to grow without wasting IP space. I'm impressed by your foresight, fellow engineer!
CA
Carey
2 years ago
Great minds think alike! Option C is the way to go for optimizing IP space and preparing for future expansion.
WH
Whitley
2 years ago
Definitely, using two /28 subnets for the Network Load Balancer is a smart way to plan for scalability.
SK
Skye
2 years ago
I agree, option C is the most efficient use of IP space while still accommodating the expected growth.
JO
Johnna
2 years ago
Option C seems like the best choice. Two /28 subnets for the Network Load Balancer will allow for future growth.
JO
Johnna
2 years ago
I think option A is the best choice because it uses the least amount of IP space.