MENU
How do you calculate a Kubernetes cluster's consistent resource capacity?
Score 2
Suggested Answer: A, B, C, D
Get Premium ACA-CloudNative Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
BL
Blossom
11 months ago
B is a solid choice, keeps it simple without missing essentials.
MI
Mitsue
11 months ago
I thought it was just A, but now I'm confused!
LE
Leonor
11 months ago
Wait, are we really considering redundancy? Seems excessive.
LE
Lenna
12 months ago
I think D is the most accurate, autoscaling is key!
CH
Chanel
12 months ago
Option C seems right, gotta factor in redundancy.
VI
Viola
1 year ago
I’m leaning towards option C because it seems to cover the essentials, but I can't recall if we discussed the impact of autoscaling in our sessions.
MA
Magnolia
1 year ago
I feel like option D could be right since it mentions autoscaling, but I'm a bit confused about how that fits into the overall calculation.
HO
Howard
1 year ago
I remember practicing a similar question, and I think it was about including average instances and redundancy for accurate capacity.
KE
Keith
1 year ago
I think the answer might involve the microservice amount and instance type, but I'm not sure if redundancy is necessary.
LI
Ligia
1 year ago
I'm pretty confident the answer is C. The question is asking for the consistent resource capacity, and that option covers all the relevant variables we need to consider.
SH
Shannan
1 year ago
Okay, let me think this through. The key is to calculate the consistent resource capacity, so I'm leaning towards C since it takes into account the core factors like microservice amount, instance type, and redundancy.
DA
Dannette
1 year ago
Hmm, I'm a bit confused. Do we need to factor in the autoscale nodes instance type as well? Option D seems to include that, but I'm not sure if that's necessary.
HE
Helaine
1 year ago
This seems straightforward - I think the answer is C, which includes the microservice amount, average instance amount, instance type, and redundancy.
UN
Una
1 year ago
Hmm, I'm a bit unsure about this one. I know Cosmos DB is designed for flexible schemas, but I'm not sure if embedding order items is the best approach here. Maybe I should think more about the tradeoffs between query efficiency and storage costs.
LA
Launa
1 year ago
Honestly, I thought using Amazon S3 would work because of its scalability, but I now realize it doesn't fit the POSIX requirement mentioned.
EL
Eloisa
1 year ago
Isn't it Verified Private Network? I might be mixing it up with something else.
NA
Nana
1 year ago
This question feels similar to one I practiced, and I think HSRP and VRRP were the focus there too. I'll go with those.
AL
Altha
1 year ago
Option C is the way to go. It's like calculating the perfect recipe for a Kubernetes stew - you need the right ingredients in the right proportions.
GE
Gene
1 year ago
Adding autoscale nodes instance type can help ensure consistent capacity for the cluster.
SE
Sena
1 year ago
Definitely, it's important to consider redundancy when calculating resource capacity.
MA
Marti
1 year ago
Option C is the way to go. It's like calculating the perfect recipe for a Kubernetes stew - you need the right ingredients in the right proportions.
AR
Art
1 year ago
If I choose Option A, my cluster will be as consistent as my coding skills - not very consistent at all!
YV
Yvonne
1 year ago
I would go with Option C to ensure the cluster has the necessary redundancy for consistent capacity.
YV
Yvonne
1 year ago
You're right, Option A might not be the best choice for calculating consistent resource capacity.
YV
Yvonne
1 year ago
Option A doesn't take into account the redundancy needed for consistent capacity.
AN
Anika
2 years ago
Option B seems too simplistic. Kubernetes clusters need to account for redundancy and autoscaling to handle workload changes.
JO
Josue
1 year ago
D) Microservice amount * Average instance amount * Instance type (e.g. 2C/4G) * Redundancy + Autoscale nodes instance type
MI
Miesha
1 year ago
C) Microservice amount * Average instance amount * Instance type (e.g. 2C/4G) * Redundancy
GE
Georgiann
1 year ago
B) Microservice amount * Average instance amount * Instance type (e.g. 2C/4G)
RO
Rosalyn
1 year ago
A) Microservice amount * Instance type (e.g. 2C/4G)
SH
Shenika
2 years ago
I'm going with Option D. Autoscaling is important for maintaining consistent resource capacity in a Kubernetes cluster.
LA
Lavonne
2 years ago
But what about autoscaling nodes instance type in option D? That could affect the capacity calculation
GA
Gaston
2 years ago
Option C looks like the right answer, it takes into account the microservice amount, average instance amount, instance type, and redundancy.
LO
Louvenia
1 year ago
Definitely, it gives a more accurate representation of the cluster's capacity.
AN
Annelle
1 year ago
I agree, it's important to consider all those variables.
LE
Leonie
1 year ago
Yeah, it covers all the important factors for calculating resource capacity.
JO
Joanna
2 years ago
I think option C is the best choice.
AS
Ashton
2 years ago
I disagree, I believe it's C) Microservice amount * Average instance amount * Instance type * Redundancy
LA
Lavonne
2 years ago
I think the answer is B) Microservice amount * Average instance amount * Instance type