MENU
Context
A container image scanner is set up on the cluster, but it's not yet fully integrated into the cluster s configuration. When complete, the container image scanner shall scan for and reject the use of vulnerable images.
Task
Given an incomplete configuration in directory /etc/kubernetes/epconfig and a functional container image scanner with HTTPS endpoint https://wakanda.local:8081 /image_policy :
1. Enable the necessary plugins to create an image policy
2. Validate the control configuration and change it to an implicit deny
3. Edit the configuration to point to the provided HTTPS endpoint correctly
Finally, test if the configuration is working by trying to deploy the vulnerable resource /root/KSSC00202/vulnerable-resource.yml.
Suggested Answer: A
Get Premium CKS Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
SA
Sanjuana
11 months ago
I thought vulnerable images were already blocked by default?
EM
Emily
11 months ago
Implicit deny is a must for security!
ER
Ernie
12 months ago
Wait, is the scanner even configured properly yet?
BE
Becky
12 months ago
Totally agree, can't skip that step.
AU
Audry
1 year ago
Make sure to enable the right plugins for the image policy!
ME
Melinda
1 year ago
I feel like testing the deployment of the vulnerable resource will be crucial to see if everything is set up correctly. I hope I remember the right command to use!
TE
Tesha
1 year ago
I’m a bit confused about editing the configuration to point to the HTTPS endpoint. Is it just a matter of changing the URL in the config file?
AL
Aleisha
1 year ago
I think we practiced something similar where we had to set an implicit deny. It’s about making sure no vulnerable images are allowed, right?
LO
Loreta
1 year ago
I remember we discussed enabling plugins for image policies, but I’m not entirely sure which ones are necessary.
CH
Christoper
1 year ago
I've worked with image scanning and policy enforcement before, so I think I've got a good handle on this. The key will be making sure I enable the right plugins and configure the HTTPS endpoint correctly. Shouldn't be too much of a challenge.
JU
Jutta
1 year ago
This seems like a tricky one. I'm not super familiar with image scanning and policy configuration, so I'll need to take my time and really understand each step before attempting to implement the solution.
SH
Shanda
1 year ago
Okay, let's break this down step-by-step. First, I'll need to enable the necessary plugins, then set the policy to implicit deny, and finally update the config to point to the HTTPS endpoint. Shouldn't be too difficult, just need to be careful with the details.
MA
Margot
1 year ago
Hmm, I'm a bit unsure about the specific steps here. I'll need to review the documentation on image policies and make sure I understand how to properly configure everything.
LE
Leslee
1 year ago
This looks like a pretty straightforward configuration task. I think I can handle it - just need to enable the right plugins, set the policy to implicit deny, and point to the HTTPS endpoint correctly.
YU
Yuriko
1 year ago
Hmm, 'wakanda.local' huh? I bet T'Challa is the one monitoring these scans. Better not mess this up!
ED
Edda
1 year ago
Wait, we have to configure an image scanner? That's like adding an extra layer of security. I'm starting to feel like a cybersecurity superhero already!
MA
Mable
1 year ago
Once the configuration is complete, the image scanner will help prevent the use of vulnerable images.
SE
Selma
1 year ago
I agree, it's like being a cybersecurity superhero protecting the cluster from vulnerabilities.
SH
Shawana
1 year ago
It's an important step to ensure that only secure container images are used.
AM
Amie
1 year ago
Yes, configuring an image scanner adds an extra layer of security to the cluster.
AN
Annmarie
1 year ago
Finally, a question that doesn't involve memorizing a gazillion Kubernetes commands. This one's got my name written all over it!
WI
Wilda
1 year ago
Let's make sure we follow the steps correctly to enable the necessary plugins and validate the control configuration.
FE
Fernanda
1 year ago
I'm excited to set up the container image scanner and test the configuration.
KA
Kara
1 year ago
I know, right? This question seems more practical and hands-on.
JU
Jutta
2 years ago
Ah, I see we need to enable the necessary plugins and set up the HTTPS endpoint. Looks like a solid challenge to test my Kubernetes skills.
LE
Leonora
1 year ago
I agree, setting up the container image scanner properly is crucial.
DO
Dorthy
1 year ago
Yes, it's definitely a good challenge to test our skills.
CY
Cyril
2 years ago
I believe enabling the necessary plugins and configuring the HTTPS endpoint are key steps to achieve this.
MA
Marisha
2 years ago
I agree, we need to ensure that only secure images are used in the cluster.
LA
Latricia
2 years ago
Hmm, this seems like a tricky one. I better double-check the configuration steps to get this right.
GE
Gerald
1 year ago
User 4: Once that's done, we can test if the configuration is working by deploying the vulnerable resource.
FE
Fernanda
1 year ago
User 3: Don't forget to edit the configuration to point to the provided HTTPS endpoint correctly.
BL
Blair
2 years ago
User 2: Yes, that's the first step. We also need to validate the control configuration and change it to an implicit deny.
RO
Rodrigo
2 years ago
User 1: I think we need to enable the necessary plugins to create an image policy.
LO
Loise
2 years ago
I think setting up the container image scanner is crucial for security.