Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

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?

AImplementing dynamic network segmentation policies

BEmploying Role-Based Access Control (RBAC) for container access

CRegular vulnerability scanning of deployed containers

DUse of immutable containers

Show Suggested 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:

Submit Cancel

Xuan

7 months ago

C is good for finding issues, but it doesn't stop changes after deployment.

upvoted 0 times

...

Meghann

8 months ago

Totally agree with D! It's a game changer for security.

upvoted 0 times

...

Gail

8 months ago

Wait, can immutable containers really prevent all modifications?

upvoted 0 times

...

Laquita

8 months ago

I think B is important too, but not for post-deployment.

upvoted 0 times

...

Catalina

8 months ago

D is the way to go! Immutable containers are key.

upvoted 0 times

...

Merissa

9 months ago

Regular vulnerability scanning seems relevant, but I don't think it directly prevents modifications after deployment.

upvoted 0 times

...

Felton

9 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

9 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

9 months ago

I think the answer might be D, using immutable containers, since they can't be changed after deployment.

upvoted 0 times

...

Aleta

9 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

9 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

9 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

9 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

9 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

9 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

1 year ago

Ah, the age-old debate: RBAC or immutable containers? I'll take the containers, please. Less meowing, more security.

upvoted 0 times

Audria

1 year ago

Immutable containers are the way to go for preventing post-deployment modifications.

upvoted 0 times

...

Eric

1 year ago

RBAC is also important for controlling access to containers.

upvoted 0 times

...

Taryn

1 year ago

I prefer using immutable containers for security.

upvoted 0 times

...

...

Tran

1 year 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

1 year ago

Regular vulnerability scanning is important, but it doesn't stop changes after deployment. Immutable containers FTW!

upvoted 0 times

Quiana

1 year ago

True, but combining it with immutable containers provides a strong security foundation.

upvoted 0 times

...

Skye

1 year ago

Regular vulnerability scanning is still important for overall security though.

upvoted 0 times

...

Roxanne

1 year ago

I agree, using immutable containers ensures that the container remains unchanged.

upvoted 0 times

...

Domitila

1 year ago

Immutable containers are the way to go for preventing post-deployment modifications.

upvoted 0 times

...

...

Brande

1 year 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

1 year ago

C) Regular vulnerability scanning of deployed containers is also important to ensure security.

upvoted 0 times

...

Gladis

1 year ago

D) Use of immutable containers is definitely the way to go for container security.

upvoted 0 times

...

...

Jaclyn

1 year ago

I'm not sure, but I think regular vulnerability scanning of deployed containers could also help ensure container security.

upvoted 0 times

...

Serina

1 year ago

I agree with Kris, immutable containers prevent post-deployment modifications.

upvoted 0 times

...

Kris

1 year ago

I think the answer is D) Use of immutable containers.

upvoted 0 times

...