New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

CSA CCSK Exam - Topic 9 Question 70 Discussion

Actual exam question for CSA's CCSK exam
Question #: 70
Topic #: 9
[All CCSK Questions]

Which practice ensures container security by preventing post-deployment modifications?

Show Suggested Answer Hide Answer
Suggested Answer: E

by Alpha at Jul 15, 2024, 06:53 AM

Limited Time Offer

25%

Off

Get Premium CCSK Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Xuan
3 months ago
C is good for finding issues, but it doesn't stop changes after deployment.
upvoted 0 times
...
Meghann
3 months ago
Totally agree with D! It's a game changer for security.
upvoted 0 times
...
Gail
3 months ago
Wait, can immutable containers really prevent all modifications?
upvoted 0 times
...
Laquita
4 months ago
I think B is important too, but not for post-deployment.
upvoted 0 times
...
Catalina
4 months ago
D is the way to go! Immutable containers are key.
upvoted 0 times
...
Merissa
4 months ago
Regular vulnerability scanning seems relevant, but I don't think it directly prevents modifications after deployment.
upvoted 0 times
...
Felton
4 months ago
I feel like I've seen a question similar to this in practice exams, and I think it was also about immutable containers.
upvoted 0 times
...
Carla
4 months ago
I'm not so sure about that. I remember something about RBAC being important for access control, but I'm not convinced it prevents modifications.
upvoted 0 times
...
Filiberto
5 months ago
I think the answer might be D, using immutable containers, since they can't be changed after deployment.
upvoted 0 times
...
Aleta
5 months ago
Ah, this is a good one. I think the key is to focus on the "preventing post-deployment modifications" part of the question. That rules out a lot of the options. I'm pretty sure the answer is D, the use of immutable containers. That's the best way to ensure the container can't be changed after it's been deployed. Feels like a solid strategy to me.
upvoted 0 times
...
Carmelina
5 months ago
Ugh, this question is really making me scratch my head. I know container security is important, but I'm not super familiar with all the different practices. I'm kind of guessing here, but maybe option C, regular vulnerability scanning of deployed containers, could help prevent post-deployment modifications? I'm not totally confident in that answer, but it's the best I can come up with.
upvoted 0 times
...
Cletus
5 months ago
Hmm, this is a tricky one. I'm not 100% sure, but I'm leaning towards option B, employing Role-Based Access Control (RBAC) for container access. That seems like it could help prevent unauthorized modifications after deployment. I'll have to think it through a bit more, but that's my initial instinct.
upvoted 0 times
...
Barrie
5 months ago
I think the key here is to focus on preventing post-deployment modifications. That rules out options like dynamic network segmentation and regular vulnerability scanning, which are more about ongoing monitoring and control. RBAC is important for access control, but doesn't directly address the issue of preventing changes after deployment. I'm going to go with option D, the use of immutable containers.
upvoted 0 times
...
Sylvie
5 months ago
I don't think it's a waste of effort to run the existing tests against the new SUT. Even if the new feature doesn't directly impact them, it's still important to verify the overall system functionality.
upvoted 0 times
...
Hubert
5 months ago
Whoa, this is a lot of information to process. I'm going to need to read through it carefully and make sure I understand all the requirements.
upvoted 0 times
...
Lyla
10 months ago
Ah, the age-old debate: RBAC or immutable containers? I'll take the containers, please. Less meowing, more security.
upvoted 0 times
Audria
9 months ago
Immutable containers are the way to go for preventing post-deployment modifications.
upvoted 0 times
...
Eric
9 months ago
RBAC is also important for controlling access to containers.
upvoted 0 times
...
Taryn
9 months ago
I prefer using immutable containers for security.
upvoted 0 times
...
...
Tran
10 months ago
I'm more of a cat person, but even I know that immutable containers are the way to go for security.
upvoted 0 times
...
Sabra
10 months ago
Regular vulnerability scanning is important, but it doesn't stop changes after deployment. Immutable containers FTW!
upvoted 0 times
Quiana
9 months ago
True, but combining it with immutable containers provides a strong security foundation.
upvoted 0 times
...
Skye
9 months ago
Regular vulnerability scanning is still important for overall security though.
upvoted 0 times
...
Roxanne
10 months ago
I agree, using immutable containers ensures that the container remains unchanged.
upvoted 0 times
...
Domitila
10 months ago
Immutable containers are the way to go for preventing post-deployment modifications.
upvoted 0 times
...
...
Brande
10 months ago
D) Use of immutable containers seems like the obvious choice here. Preventing post-deployment modifications is key to container security.
upvoted 0 times
Dick
10 months ago
C) Regular vulnerability scanning of deployed containers is also important to ensure security.
upvoted 0 times
...
Gladis
10 months ago
D) Use of immutable containers is definitely the way to go for container security.
upvoted 0 times
...
...
Jaclyn
11 months ago
I'm not sure, but I think regular vulnerability scanning of deployed containers could also help ensure container security.
upvoted 0 times
...
Serina
11 months ago
I agree with Kris, immutable containers prevent post-deployment modifications.
upvoted 0 times
...
Kris
11 months ago
I think the answer is D) Use of immutable containers.
upvoted 0 times
...

Save Cancel