ISC CCSP Dumps
ISC CCSP Practice Test 59
Question 580
A government benefit gateway sees automated high-volume calls from valid low-privilege credentials. Suppose the team makes this shortcut instead: Assume an HTTPS endpoint can safely skip user authorization and request throttling. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: D
This failure concerns another scenario: A bank's serverless functions all reuse a broad database administrator password stored in their source code. In the stated case: A government benefit gateway sees automated high-volume calls from valid low-privilege credentials. The relevant consequence is: Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity. The control that prevents it is: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries.
This failure concerns another scenario: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. In the stated case: A government benefit gateway sees automated high-volume calls from valid low-privilege credentials. The relevant consequence is: Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity. The control that prevents it is: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries.
This failure concerns another scenario: A customer support assistant reads uploaded tickets and has permission to change billing access lists. In the stated case: A government benefit gateway sees automated high-volume calls from valid low-privilege credentials. The relevant consequence is: Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity. The control that prevents it is: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries.
Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity. This is the risk in the stated situation: A government benefit gateway sees automated high-volume calls from valid low-privilege credentials. The risky shortcut is: Assume an HTTPS endpoint can safely skip user authorization and request throttling. Prevent it by: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries.
Question 581
A university deploys student-made web containers with access to the host container engine socket. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: A
Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. The technical reason is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. The stated condition is: A university deploys student-made web containers with access to the host container engine socket. Confirm the result by: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This action is appropriate in a different case: A clinic's internal appointment API trusts any caller from the cluster pod network. There, the reason is: Private cluster networks can still carry attacker lateral movement if internal callers are not authenticated or scoped. The current case is: A university deploys student-made web containers with access to the host container engine socket. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This action is appropriate in a different case: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. There, the reason is: Cloud API routes often expose object identifiers, and a valid login does not authorize access to every tenant object. The current case is: A university deploys student-made web containers with access to the host container engine socket. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This action is appropriate in a different case: A customer support assistant reads uploaded tickets and has permission to change billing access lists. There, the reason is: A model can follow malicious instructions embedded in lower-trust text unless tools, data and privileges are bounded outside the prompt. The current case is: A university deploys student-made web containers with access to the host container engine socket. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Question 582
A university deploys student-made web containers with access to the host container engine socket. An engineer recommends: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: B
This principle explains a different technical intervention: Teach application teams to treat retrieved documents and model output as untrusted inputs before triggering sensitive cloud actions. It applies to: A customer support assistant reads uploaded tickets and has permission to change billing access lists. The actual case is: A university deploys student-made web containers with access to the host container engine socket. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. That mechanism explains the decision: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. In the reported situation: A university deploys student-made web containers with access to the host container engine socket. Confirmation requires: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This principle explains a different technical intervention: Translate business and privacy needs into measurable authentication, authorization, encryption and recovery criteria at the start of the SDLC. It applies to: A medical SaaS startup writes an application first and asks later how to prevent staff from viewing patient data. The actual case is: A university deploys student-made web containers with access to the host container engine socket. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
This principle explains a different technical intervention: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. It applies to: A finance platform releases API changes daily but schedules its only security test annually. The actual case is: A university deploys student-made web containers with access to the host container engine socket. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
Question 583
A university deploys student-made web containers with access to the host container engine socket. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: C
This observation would verify a different remedy: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. That remedy applies to: A finance platform releases API changes daily but schedules its only security test annually. The present condition is: A university deploys student-made web containers with access to the host container engine socket. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This observation would verify a different remedy: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. That remedy applies to: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The present condition is: A university deploys student-made web containers with access to the host container engine socket. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets. This check directly tests: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. The underlying behavior is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. The case is: A university deploys student-made web containers with access to the host container engine socket.
This observation would verify a different remedy: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. That remedy applies to: A university uses shared infrastructure templates containing hard-coded production API tokens. The present condition is: A university deploys student-made web containers with access to the host container engine socket. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
Question 584
A university deploys student-made web containers with access to the host container engine socket. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: D
This proposed shortcut concerns a separate case: A university uses shared infrastructure templates containing hard-coded production API tokens. The risk in this question concerns: A university deploys student-made web containers with access to the host container engine socket. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This proposed shortcut concerns a separate case: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. The risk in this question concerns: A university deploys student-made web containers with access to the host container engine socket. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This proposed shortcut concerns a separate case: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The risk in this question concerns: A university deploys student-made web containers with access to the host container engine socket. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. This shortcut is unsafe for: A university deploys student-made web containers with access to the host container engine socket. The resulting failure can be: One compromised container can access host credentials or neighboring workloads. The safer response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Question 585
A university deploys student-made web containers with access to the host container engine socket. Suppose the team makes this shortcut instead: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: A
One compromised container can access host credentials or neighboring workloads. This is the risk in the stated situation: A university deploys student-made web containers with access to the host container engine socket. The risky shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Prevent it by: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This failure concerns another scenario: A property portal's normal customer checkout succeeds but users can alter another account's billing address. In the stated case: A university deploys student-made web containers with access to the host container engine socket. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This failure concerns another scenario: A healthcare startup uses an unpinned container image that an unknown publisher can replace. In the stated case: A university deploys student-made web containers with access to the host container engine socket. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This failure concerns another scenario: A retail API terminates TLS correctly but accepts any account number from a logged-in user. In the stated case: A university deploys student-made web containers with access to the host container engine socket. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Question 586
A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: B
This action is appropriate in a different case: A customer support assistant reads uploaded tickets and has permission to change billing access lists. There, the reason is: A model can follow malicious instructions embedded in lower-trust text unless tools, data and privileges are bounded outside the prompt. The current case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. The technical reason is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. The stated condition is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Confirm the result by: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This action is appropriate in a different case: A medical SaaS startup writes an application first and asks later how to prevent staff from viewing patient data. There, the reason is: Security requirements discovered only after deployment become expensive or incompatible with existing application architecture. The current case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This action is appropriate in a different case: A finance platform releases API changes daily but schedules its only security test annually. There, the reason is: Frequent deployment creates repeated change risk, so security review must track each material feature and dependency update. The current case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The appropriate response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Question 587
A payment service requires one writable scratch directory but the image runs as root with broad host mounts. An engineer recommends: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: C
This principle explains a different technical intervention: Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist. It applies to: A finance platform releases API changes daily but schedules its only security test annually. The actual case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
This principle explains a different technical intervention: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation. It applies to: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. The actual case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. That mechanism explains the decision: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. In the reported situation: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Confirmation requires: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This principle explains a different technical intervention: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. It applies to: A university uses shared infrastructure templates containing hard-coded production API tokens. The actual case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The mechanism relevant here is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope.
Question 588
A payment service requires one writable scratch directory but the image runs as root with broad host mounts. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: D
This observation would verify a different remedy: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. That remedy applies to: A university uses shared infrastructure templates containing hard-coded production API tokens. The present condition is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This observation would verify a different remedy: Run complementary source, dependency and runtime security tests with severity-based release gates. That remedy applies to: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. The present condition is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
This observation would verify a different remedy: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests. That remedy applies to: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The present condition is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. To assess it, check: Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets.
Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets. This check directly tests: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. The underlying behavior is: Container namespaces share a host kernel, and unnecessary privilege can expose host resources beyond the intended application scope. The case is: A payment service requires one writable scratch directory but the image runs as root with broad host mounts.
Question 589
A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: A
Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. This shortcut is unsafe for: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The resulting failure can be: One compromised container can access host credentials or neighboring workloads. The safer response is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This proposed shortcut concerns a separate case: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The risk in this question concerns: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This proposed shortcut concerns a separate case: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The risk in this question concerns: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This proposed shortcut concerns a separate case: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The risk in this question concerns: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Here the unsafe shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Use this response instead: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Question 590
A payment service requires one writable scratch directory but the image runs as root with broad host mounts. Suppose the team makes this shortcut instead: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: B
This failure concerns another scenario: A retail API terminates TLS correctly but accepts any account number from a logged-in user. In the stated case: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
One compromised container can access host credentials or neighboring workloads. This is the risk in the stated situation: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The risky shortcut is: Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging. Prevent it by: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This failure concerns another scenario: A multinational enterprise adds SaaS login federation but accidentally maps all staff to a cloud admin group. In the stated case: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
This failure concerns another scenario: A bank's serverless functions all reuse a broad database administrator password stored in their source code. In the stated case: A payment service requires one writable scratch directory but the image runs as root with broad host mounts. The relevant consequence is: One compromised container can access host credentials or neighboring workloads. The control that prevents it is: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported.
Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests
- ISC CCSP Practice Test 57 - 10 Questions (Last Reviewed 20-Nov-2026)
- ISC CCSP Practice Test 58 - 10 Questions (Last Reviewed 19-Nov-2026)
- ISC CCSP Practice Test 59 - 10 Questions (Last Reviewed 18-Nov-2026)
- ISC CCSP Practice Test 60 - 10 Questions (Last Reviewed 17-Nov-2026)
- ISC CCSP Practice Test 61 - 10 Questions (Last Reviewed 16-Nov-2026)