ISC CCSP Dumps
ISC CCSP Practice Test 57
Question 560
A cloud storage app adds an upload endpoint without negative tests against unauthorized object overwrite. Suppose the team makes this shortcut instead: Test only the happy-path administrator action and label the entire feature security validated. 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 cloud storage app adds an upload endpoint without negative tests against unauthorized object overwrite. The relevant consequence is: A minor application change silently reintroduces horizontal or vertical privilege escalation. The control that prevents it is: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests.
This failure concerns another scenario: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. In the stated case: A cloud storage app adds an upload endpoint without negative tests against unauthorized object overwrite. The relevant consequence is: A minor application change silently reintroduces horizontal or vertical privilege escalation. The control that prevents it is: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests.
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 cloud storage app adds an upload endpoint without negative tests against unauthorized object overwrite. The relevant consequence is: A minor application change silently reintroduces horizontal or vertical privilege escalation. The control that prevents it is: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests.
A minor application change silently reintroduces horizontal or vertical privilege escalation. This is the risk in the stated situation: A cloud storage app adds an upload endpoint without negative tests against unauthorized object overwrite. The risky shortcut is: Test only the happy-path administrator action and label the entire feature security validated. Prevent it by: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests.
Question 561
A healthcare startup uses an unpinned container image that an unknown publisher can replace. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: A
Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. The technical reason is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. The stated condition is: A healthcare startup uses an unpinned container image that an unknown publisher can replace. Confirm the result by: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
This action is appropriate in a different case: A retail API terminates TLS correctly but accepts any account number from a logged-in user. There, the reason is: TLS protects transport but cannot determine whether an authenticated caller may access a particular business object or issue excessive requests. The current case is: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Question 562
A healthcare startup uses an unpinned container image that an unknown publisher can replace. An engineer recommends: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. 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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. That mechanism explains the decision: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. In the reported situation: A healthcare startup uses an unpinned container image that an unknown publisher can replace. Confirmation requires: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
Question 563
A healthcare startup uses an unpinned container image that an unknown publisher can replace. 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 healthcare startup uses an unpinned container image that an unknown publisher can replace. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image. This check directly tests: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. The underlying behavior is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. The case is: A healthcare startup uses an unpinned container image that an unknown publisher can replace.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
Question 564
A healthcare startup uses an unpinned container image that an unknown publisher can replace. 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 healthcare startup uses an unpinned container image that an unknown publisher can replace. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. This shortcut is unsafe for: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The resulting failure can be: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The safer response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Question 565
A healthcare startup uses an unpinned container image that an unknown publisher can replace. Suppose the team makes this shortcut instead: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: A
A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. This is the risk in the stated situation: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The risky shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Prevent it by: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 healthcare startup uses an unpinned container image that an unknown publisher can replace. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
This failure concerns another scenario: A university deploys student-made web containers with access to the host container engine socket. In the stated case: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Question 566
A bank must trace production API packages to reproducible signed builds for supplier assurance. 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 bank must trace production API packages to reproducible signed builds for supplier assurance. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. The technical reason is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. The stated condition is: A bank must trace production API packages to reproducible signed builds for supplier assurance. Confirm the result by: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The appropriate response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Question 567
A bank must trace production API packages to reproducible signed builds for supplier assurance. An engineer recommends: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. 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 bank must trace production API packages to reproducible signed builds for supplier assurance. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. That mechanism explains the decision: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. In the reported situation: A bank must trace production API packages to reproducible signed builds for supplier assurance. Confirmation requires: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The mechanism relevant here is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues.
Question 568
A bank must trace production API packages to reproducible signed builds for supplier assurance. 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 bank must trace production API packages to reproducible signed builds for supplier assurance. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. To assess it, check: Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image.
Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image. This check directly tests: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. The underlying behavior is: Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues. The case is: A bank must trace production API packages to reproducible signed builds for supplier assurance.
Question 569
A bank must trace production API packages to reproducible signed builds for supplier assurance. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: A
Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. This shortcut is unsafe for: A bank must trace production API packages to reproducible signed builds for supplier assurance. The resulting failure can be: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The safer response is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
This proposed shortcut concerns a separate case: A university deploys student-made web containers with access to the host container engine socket. The risk in this question concerns: A bank must trace production API packages to reproducible signed builds for supplier assurance. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
This proposed shortcut concerns a separate case: A clinic's internal appointment API trusts any caller from the cluster pod network. The risk in this question concerns: A bank must trace production API packages to reproducible signed builds for supplier assurance. Here the unsafe shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Use this response instead: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Question 570
A bank must trace production API packages to reproducible signed builds for supplier assurance. Suppose the team makes this shortcut instead: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: B
This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A bank must trace production API packages to reproducible signed builds for supplier assurance. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. This is the risk in the stated situation: A bank must trace production API packages to reproducible signed builds for supplier assurance. The risky shortcut is: Pull production containers from an untrusted public tag solely because the image name resembles a trusted project. Prevent it by: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
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 bank must trace production API packages to reproducible signed builds for supplier assurance. The relevant consequence is: A substituted or vulnerable dependency enters the application supply chain without a reliable integrity trail. The control that prevents it is: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images.
Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests
- ISC CCSP Practice Test 55 - 10 Questions (Last Reviewed 26-Sep-2026)
- ISC CCSP Practice Test 56 - 10 Questions (Last Reviewed 25-Sep-2026)
- 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)