Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Linux Foundation Exam CKAD Topic 10 Question 36 Discussion

Actual exam question for Linux Foundation's CKAD exam
Question #: 36
Topic #: 10
[All CKAD Questions]

Refer to Exhibit.

Context

You are asked to prepare a Canary deployment for testing a new application release.

Task:

A Service named krill-Service in the goshark namespace points to 5 pod created by the Deployment named current-krill-deployment

1) Create an identical Deployment named canary-kill-deployment, in the same namespace.

2) Modify the Deployment so that:

-A maximum number of 10 pods run in the goshawk namespace.

-40% of the krill-service 's traffic goes to the canary-krill-deployment pod(s)

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Fidelia
5 months ago
That's correct. We also need to ensure 40% of the traffic goes to the canary deployment.
upvoted 0 times
...
Tamekia
5 months ago
I believe we need to set the maximum number of pods to 10 in the namespace.
upvoted 0 times
...
Kenneth
5 months ago
Yes, we have to modify the Deployment to control the traffic percentage.
upvoted 0 times
...
Fidelia
5 months ago
I think we need to create a new Deployment for the Canary deployment.
upvoted 0 times
...
Tamekia
6 months ago
This question is tricky. I'm not sure where to start.
upvoted 0 times
...
Jarvis
6 months ago
The solution should involve creating a new Deployment and updating the traffic split.
upvoted 0 times
...
Mable
6 months ago
And we have to limit the number of pods to 10.
upvoted 0 times
...
Paola
7 months ago
Yes, we need to ensure only 40% of the traffic goes to the canary pods.
upvoted 0 times
...
Jarvis
7 months ago
I think we need to create a new Deployment and modify the traffic split.
upvoted 0 times
...
Mable
7 months ago
I agree, Canary deployments can be complex.
upvoted 0 times
...
Paola
7 months ago
This question seems tricky.
upvoted 0 times
Dorian
7 months ago
That's correct. Making sure we follow all the instructions is key.
upvoted 0 times
...
Carlota
7 months ago
Do we also need to limit the number of pods to 10 in the namespace?
upvoted 0 times
...
Melissia
7 months ago
Yes, and then we need to modify it so that 40% of the traffic goes to the canary pod.
upvoted 0 times
...
Antonio
7 months ago
I think we need to create an identical Deployment first.
upvoted 0 times
...
...
Laurena
8 months ago
This is the kind of question that really separates the Kubernetes masters from the novices. I bet the folks who've been tinkering with Canary deployments in production are going to fly through this one.
upvoted 0 times
...
Cory
8 months ago
Okay, I've got a plan. First, we create the new Deployment with the correct pod limit. Then, we use a Service with a weighted load-balancing strategy to divvy up the traffic. Simple as that, right? *chuckles*
upvoted 0 times
...
Elly
8 months ago
Hmm, the traffic split is the tricky part, if you ask me. How do we make sure we're sending 40% to the new Deployment without going over? Gotta be some nifty networking tricks involved here.
upvoted 0 times
...
Naomi
8 months ago
I'm feeling pretty confident about this one. The instructions are clear, and the images are super helpful. As long as we pay attention to the details, I think we've got a shot at nailing this.
upvoted 0 times
...
William
8 months ago
Alright, let's break this down. We need to create an identical Deployment, but with a few twists. Limiting the pod count to 10 and splitting the traffic between the original and the new Deployment? Sounds like a delicate balancing act.
upvoted 0 times
...
Melissia
8 months ago
Whoa, this question is a real doozy! Canary deployments, huh? Sounds like we've got our work cut out for us. I wonder how many of us are going to ace this one.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77