MENU
You are ready to deploy a new feature of a web-based application to production. You want to use Google Kubernetes Engine (GKE) to perform a phased rollout to half of the web server pods.
What should you do?
Suggested Answer: B
Get Premium Professional Cloud DevOps Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
BR
Brock
11 months ago
Wait, are we really using half the pods? That’s bold!
LI
Lili
11 months ago
D? Really? That seems like overkill for this.
DE
Denny
11 months ago
B sounds interesting, but not sure it fits this scenario.
LA
Latrice
11 months ago
I think C might be better for managing replicas.
BE
Bette
12 months ago
A is the way to go for phased rollouts!
VI
Virgilio
12 months ago
Stateful sets are usually for stateful applications, right? I don't think that's applicable here, but I could be wrong.
MA
Malinda
1 year ago
Node taints with NoExecute sounds familiar, but I don't think that's what we want for a phased rollout. It seems more about scheduling than deployment.
TA
Tamar
1 year ago
I remember practicing with replica sets in deployments, but I can't recall if they specifically help with phased rollouts like this one.
RO
Roxane
1 year ago
I think a partitioned rolling update might be the right choice since it allows for phased rollouts, but I'm not entirely sure if it's the best option for GKE.
DA
Darell
1 year ago
A stateful set with parallel pod management policy could work, but I'm not sure if that's the right tool for a web server deployment. I'll need to double-check the requirements.
EL
Elena
1 year ago
Using Node taints with NoExecute sounds like an interesting approach, but I'm not sure if that's the best fit for a phased rollout. I'll have to review the details on that.
XE
Xenia
1 year ago
Hmm, I'm a bit confused about the difference between a rolling update and a replica set. I'll have to think this through carefully.
GE
German
1 year ago
I'm pretty confident this is a rolling update scenario, so I'll go with option A.
JA
Javier
1 year ago
This one seems pretty straightforward. I'm pretty sure the RSA Archer Public Sector solution helps organizations reach compliance with FISMA.
AM
Amina
1 year ago
This seems like a straightforward question. The satisfaction scale is clearly ordinal, with 1 being the lowest and 5 being the highest. I'm confident I can select the right answer.
BR
Brittni
1 year ago
I think if the logs are full, they might not show any new events, which could make debugging harder, but I'm not entirely sure if that's the main issue here.
JU
Junita
1 year ago
Okay, let me think this through. The key is to identify which of the given strategies are valid according to the ISTQB syllabus. I'll eliminate the options that don't match.
SO
Solange
1 year ago
I'm just here for the free donuts. Oh, the question? Hmm, I'd go with A. Sounds like the most straightforward way to do a phased rollout.
GL
Glenna
1 year ago
D is an interesting option, but a stateful set with parallel pod management policy seems overkill for a simple web server deployment. Isn't that more for stateful applications?
IL
Ilda
1 year ago
Agreed, let's go with a deployment and rolling update strategy for the phased rollout.
KA
Kati
1 year ago
That's a good point, a rolling update strategy would be more suitable for this scenario.
KA
Kanisha
1 year ago
That way you can easily control the number of pods being updated at a time.
TI
Tijuana
1 year ago
You could consider using a Deployment with a rolling update strategy instead.
SO
Socorro
1 year ago
I agree, using a stateful set for a simple web server deployment does seem like overkill.
JU
Jutta
1 year ago
You could try using a deployment with a rolling update strategy instead.
JO
Jordan
1 year ago
I think you're right, using a stateful set might be too much for a simple web server deployment.
HA
Harley
1 year ago
C is a nice idea, but a replica set alone won't give you the control you need for a phased rollout. I'd want something more specific to the deployment process.
LA
Laurel
1 year ago
Consider using Kubernetes Ingress to manage traffic routing during the rollout.
CO
Corinne
1 year ago
You can use Deployment strategies like RollingUpdate to control the deployment process.
MA
Malcom
1 year ago
Use Kubernetes Deployment objects to manage the rollout process.
LI
Lizette
1 year ago
B sounds interesting, but I'm not sure Node taints with NoExecute are the right tool for this task. Shouldn't we be looking at something more deployment-focused?
ER
Eric
1 year ago
A: Let's go with Deployments then for the rollout to production.
EL
Elouise
1 year ago
B: That's a good point. Deployments would be more deployment-focused than Node taints.
FL
Floyd
1 year ago
A: I think we should consider using Kubernetes Deployments for a phased rollout.
LI
Lisbeth
1 year ago
I think option A is the way to go. A partitioned rolling update allows you to gradually roll out the new feature to a subset of the pods, which seems perfect for this scenario.
VI
Vicente
2 years ago
I prefer using a replica set in the deployment specification for better scalability.
RO
Robt
2 years ago
I agree with Barb, it allows us to control the rollout process.
BA
Barb
2 years ago
I think we should use a partitioned rolling update.