Practice Exams:

ISC CCSP Dumps

EXAM: Certified Cloud Security Professional (CCSP)
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

CCSP Premium Bundle


  • Premium File 512 Questions & Answers
  • Training Course 43 Lectures
  • Study Guide 571 Pages

ISC CCSP Practice Test 62

Question 610

A research portal accepts SSO assertions for a different application audience without verifying token scope. Suppose the team makes this shortcut instead: Grant every federated employee global administrator privileges because the identity provider confirmed login. Which outcome is the most likely direct consequence?

  1. Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity
  2. A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement
  3. One compromised container can access host credentials or neighboring workloads
  4. A compromised low-value service pivots to sensitive internal APIs without user-facing controls

Answer & Explanations

Correct answer: B

A.

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 research portal accepts SSO assertions for a different application audience without verifying token scope. The relevant consequence is: A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement. The control that prevents it is: Integrate cloud applications with a trusted identity provider using signed federation assertions, MFA and least-privilege role mapping.

B.

A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement. This is the risk in the stated situation: A research portal accepts SSO assertions for a different application audience without verifying token scope. The risky shortcut is: Grant every federated employee global administrator privileges because the identity provider confirmed login. Prevent it by: Integrate cloud applications with a trusted identity provider using signed federation assertions, MFA and least-privilege role mapping.

C.

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 research portal accepts SSO assertions for a different application audience without verifying token scope. The relevant consequence is: A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement. The control that prevents it is: Integrate cloud applications with a trusted identity provider using signed federation assertions, MFA and least-privilege role mapping.

D.

This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A research portal accepts SSO assertions for a different application audience without verifying token scope. The relevant consequence is: A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement. The control that prevents it is: Integrate cloud applications with a trusted identity provider using signed federation assertions, MFA and least-privilege role mapping.

Question 611

A bank's serverless functions all reuse a broad database administrator password stored in their source code. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Teach application teams to treat retrieved documents and model output as untrusted inputs before triggering sensitive cloud actions
  2. Translate business and privacy needs into measurable authentication, authorization, encryption and recovery criteria at the start of the SDLC
  3. Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials
  4. Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist

Answer & Explanations

Correct answer: C

A.

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's serverless functions all reuse a broad database administrator password stored in their source code. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

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's serverless functions all reuse a broad database administrator password stored in their source code. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. The technical reason is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. The stated condition is: A bank's serverless functions all reuse a broad database administrator password stored in their source code. Confirm the result by: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

D.

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's serverless functions all reuse a broad database administrator password stored in their source code. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

Question 612

A bank's serverless functions all reuse a broad database administrator password stored in their source code. An engineer recommends: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. Which technical explanation most directly justifies this recommendation?

  1. Frequent deployment creates repeated change risk, so security review must track each material feature and dependency update
  2. Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats
  3. Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation
  4. Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure

Answer & Explanations

Correct answer: D

A.

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's serverless functions all reuse a broad database administrator password stored in their source code. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

B.

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's serverless functions all reuse a broad database administrator password stored in their source code. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

C.

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's serverless functions all reuse a broad database administrator password stored in their source code. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

D.

Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. That mechanism explains the decision: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. In the reported situation: A bank's serverless functions all reuse a broad database administrator password stored in their source code. Confirmation requires: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

Question 613

A bank's serverless functions all reuse a broad database administrator password stored in their source code. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected
  2. Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment
  3. Inject a safe known vulnerable dependency and a staging runtime flaw and verify each matching scanner detects its own class of risk
  4. Re-run a role-bypass abuse case after each release and verify denial and logging remain effective

Answer & Explanations

Correct answer: A

A.

Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected. This check directly tests: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. The underlying behavior is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. The case is: A bank's serverless functions all reuse a broad database administrator password stored in their source code.

B.

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's serverless functions all reuse a broad database administrator password stored in their source code. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

C.

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's serverless functions all reuse a broad database administrator password stored in their source code. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

D.

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's serverless functions all reuse a broad database administrator password stored in their source code. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

Question 614

A bank's serverless functions all reuse a broad database administrator password stored in their source code. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Test only the happy-path administrator action and label the entire feature security validated
  2. Put one production cloud administrator API key in every microservice image to make deployment easier
  3. Pull production containers from an untrusted public tag solely because the image name resembles a trusted project
  4. Assume an HTTPS endpoint can safely skip user authorization and request throttling

Answer & Explanations

Correct answer: B

A.

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's serverless functions all reuse a broad database administrator password stored in their source code. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

Put one production cloud administrator API key in every microservice image to make deployment easier. This shortcut is unsafe for: A bank's serverless functions all reuse a broad database administrator password stored in their source code. The resulting failure can be: A leaked image or source bundle grants enduring privileged access across unrelated services. The safer response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

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 bank's serverless functions all reuse a broad database administrator password stored in their source code. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

D.

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 bank's serverless functions all reuse a broad database administrator password stored in their source code. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

Question 615

A bank's serverless functions all reuse a broad database administrator password stored in their source code. Suppose the team makes this shortcut instead: Put one production cloud administrator API key in every microservice image to make deployment easier. Which outcome is the most likely direct consequence?

  1. Attackers use stolen low-privilege tokens to read other records or exhaust backend capacity
  2. One compromised container can access host credentials or neighboring workloads
  3. A leaked image or source bundle grants enduring privileged access across unrelated services
  4. A compromised low-value service pivots to sensitive internal APIs without user-facing controls

Answer & Explanations

Correct answer: C

A.

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 bank's serverless functions all reuse a broad database administrator password stored in their source code. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

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 bank's serverless functions all reuse a broad database administrator password stored in their source code. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

A leaked image or source bundle grants enduring privileged access across unrelated services. This is the risk in the stated situation: A bank's serverless functions all reuse a broad database administrator password stored in their source code. The risky shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Prevent it by: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

D.

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's serverless functions all reuse a broad database administrator password stored in their source code. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

Question 616

A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Use risk-based secure design and code validation throughout agile iterations instead of relying on one end-stage checklist
  2. Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation
  3. Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied
  4. Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials

Answer & Explanations

Correct answer: D

A.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

This action is appropriate in a different case: A multi-tenant booking API accepts customer resource IDs without modeling horizontal access attacks. There, the reason is: Threat modeling connects system architecture to plausible abuse paths so authorization and rate-limit controls address actual threats. The current case is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

This action is appropriate in a different case: A university uses shared infrastructure templates containing hard-coded production API tokens. There, the reason is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The current case is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The appropriate response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

D.

Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. The technical reason is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. The stated condition is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Confirm the result by: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

Question 617

A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. An engineer recommends: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. Which technical explanation most directly justifies this recommendation?

  1. Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure
  2. Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation
  3. Static analysis finds code patterns, software composition analysis checks third-party components and dynamic testing observes a deployed application's behavior
  4. Functional success does not establish that unauthorized users cannot trigger the same operation through alternate inputs

Answer & Explanations

Correct answer: A

A.

Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. That mechanism explains the decision: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. In the reported situation: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Confirmation requires: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

B.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

C.

This principle explains a different technical intervention: Run complementary source, dependency and runtime security tests with severity-based release gates. It applies to: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. The actual case is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

D.

This principle explains a different technical intervention: Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests. It applies to: A property portal's normal customer checkout succeeds but users can alter another account's billing address. The actual case is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The mechanism relevant here is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure.

Question 618

A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Re-run a role-bypass abuse case after each release and verify denial and logging remain effective
  2. Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected
  3. Validate a test artifact signature and SBOM against expected build identity and reject an unsigned modified image
  4. Use a test client to verify invalid tokens, unauthorized object IDs and over-limit calls fail with correct logged outcomes

Answer & Explanations

Correct answer: B

A.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

B.

Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected. This check directly tests: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials. The underlying behavior is: Long-lived shared secrets in application code are difficult to revoke and amplify the impact of source or artifact exposure. The case is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline.

C.

This observation would verify a different remedy: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. That remedy applies to: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The present condition is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

D.

This observation would verify a different remedy: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries. That remedy applies to: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The present condition is: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. To assess it, check: Rotate a staging secret and prove the application resumes with the new value while the old credential is rejected.

Question 619

A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Assume an HTTPS endpoint can safely skip user authorization and request throttling
  2. Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging
  3. Put one production cloud administrator API key in every microservice image to make deployment easier
  4. Allow every workload in the Kubernetes cluster to call every financial API merely because traffic stays internal

Answer & Explanations

Correct answer: C

A.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

Put one production cloud administrator API key in every microservice image to make deployment easier. This shortcut is unsafe for: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The resulting failure can be: A leaked image or source bundle grants enduring privileged access across unrelated services. The safer response is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

D.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Here the unsafe shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Use this response instead: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

Question 620

A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. Suppose the team makes this shortcut instead: Put one production cloud administrator API key in every microservice image to make deployment easier. Which outcome is the most likely direct consequence?

  1. A compromised low-value service pivots to sensitive internal APIs without user-facing controls
  2. Authenticated attackers retrieve or modify other tenants' application records by changing resource IDs
  3. An attacker uses an ordinary content upload to trigger unauthorized tool actions or data disclosure
  4. A leaked image or source bundle grants enduring privileged access across unrelated services

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A clinic's internal appointment API trusts any caller from the cluster pod network. In the stated case: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

B.

This failure concerns another scenario: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. In the stated case: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

C.

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 laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The relevant consequence is: A leaked image or source bundle grants enduring privileged access across unrelated services. The control that prevents it is: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

D.

A leaked image or source bundle grants enduring privileged access across unrelated services. This is the risk in the stated situation: A laboratory needs to rotate a vendor integration token without taking every unrelated application offline. The risky shortcut is: Put one production cloud administrator API key in every microservice image to make deployment easier. Prevent it by: Use workload identities or managed secrets vaults with automatic rotation and least-privilege access instead of embedded static credentials.

Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests