MENU
Which practice ensures container security by preventing post-deployment modifications?
Suggested Answer: E
Get Premium CCSK Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
XU
Xuan
10 months ago
C is good for finding issues, but it doesn't stop changes after deployment.
ME
Meghann
11 months ago
Totally agree with D! It's a game changer for security.
GA
Gail
11 months ago
Wait, can immutable containers really prevent all modifications?
LA
Laquita
11 months ago
I think B is important too, but not for post-deployment.
CA
Catalina
11 months ago
D is the way to go! Immutable containers are key.
ME
Merissa
12 months ago
Regular vulnerability scanning seems relevant, but I don't think it directly prevents modifications after deployment.
FE
Felton
12 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.
CA
Carla
12 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.
FI
Filiberto
1 year ago
I think the answer might be D, using immutable containers, since they can't be changed after deployment.
AL
Aleta
1 year 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.
CA
Carmelina
1 year 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.
CL
Cletus
1 year 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.
BA
Barrie
1 year 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.
SY
Sylvie
1 year 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.
HU
Hubert
1 year 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.
LY
Lyla
1 year ago
Ah, the age-old debate: RBAC or immutable containers? I'll take the containers, please. Less meowing, more security.
AU
Audria
1 year ago
Immutable containers are the way to go for preventing post-deployment modifications.
ER
Eric
1 year ago
RBAC is also important for controlling access to containers.
TA
Taryn
1 year ago
I prefer using immutable containers for security.
TR
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.
SA
Sabra
1 year ago
Regular vulnerability scanning is important, but it doesn't stop changes after deployment. Immutable containers FTW!
QU
Quiana
1 year ago
True, but combining it with immutable containers provides a strong security foundation.
SK
Skye
1 year ago
Regular vulnerability scanning is still important for overall security though.
RO
Roxanne
1 year ago
I agree, using immutable containers ensures that the container remains unchanged.
DO
Domitila
1 year ago
Immutable containers are the way to go for preventing post-deployment modifications.
BR
Brande
1 year ago
D) Use of immutable containers seems like the obvious choice here. Preventing post-deployment modifications is key to container security.
DI
Dick
1 year ago
C) Regular vulnerability scanning of deployed containers is also important to ensure security.
GL
Gladis
1 year ago
D) Use of immutable containers is definitely the way to go for container security.
JA
Jaclyn
2 years ago
I'm not sure, but I think regular vulnerability scanning of deployed containers could also help ensure container security.
SE
Serina
2 years ago
I agree with Kris, immutable containers prevent post-deployment modifications.
KR
Kris
2 years ago
I think the answer is D) Use of immutable containers.