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 54

Question 530

A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. Suppose the team makes this shortcut instead: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Which outcome is the most likely direct consequence?

  1. A compromised low-value service pivots to sensitive internal APIs without user-facing controls
  2. An overlooked cross-tenant API path is released without a suitable authorization or monitoring control
  3. A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement
  4. A leaked image or source bundle grants enduring privileged access across unrelated services

Answer & Explanations

Correct answer: B

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 hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

B.

An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. This is the risk in the stated situation: A hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The risky shortcut is: Treat a network diagram with no identities or trust boundaries as a completed application threat model. Prevent it by: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

C.

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 hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

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 hospital designs a cloud workflow that crosses private and internet-facing trust boundaries. The relevant consequence is: An overlooked cross-tenant API path is released without a suitable authorization or monitoring control. The control that prevents it is: Perform structured threat modeling of exposed trust boundaries and select controls for spoofing, tampering, disclosure, denial and privilege escalation.

Question 531

A university uses shared infrastructure templates containing hard-coded production API tokens. 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. Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied
  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 university uses shared infrastructure templates containing hard-coded production API tokens. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

C.

Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. The technical reason is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The stated condition is: A university uses shared infrastructure templates containing hard-coded production API tokens. Confirm the result by: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

Question 532

A university uses shared infrastructure templates containing hard-coded production API tokens. An engineer recommends: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. 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. Static analysis finds code patterns, software composition analysis checks third-party components and dynamic testing observes a deployed application's behavior
  3. Functional success does not establish that unauthorized users cannot trigger the same operation through alternate inputs
  4. Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation

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 university uses shared infrastructure templates containing hard-coded production API tokens. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

B.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

C.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

D.

Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. That mechanism explains the decision: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. In the reported situation: A university uses shared infrastructure templates containing hard-coded production API tokens. Confirmation requires: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

Question 533

A university uses shared infrastructure templates containing hard-coded production API tokens. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment
  2. Re-run a role-bypass abuse case after each release and verify denial and logging remain effective
  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: A

A.

Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment. This check directly tests: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. The underlying behavior is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The case is: A university uses shared infrastructure templates containing hard-coded production API tokens.

B.

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 university uses shared infrastructure templates containing hard-coded production API tokens. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

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 university uses shared infrastructure templates containing hard-coded production API tokens. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

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 university uses shared infrastructure templates containing hard-coded production API tokens. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

Question 534

A university uses shared infrastructure templates containing hard-coded production API tokens. 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. Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review
  3. Run every internet-facing container as privileged with the host filesystem mounted to simplify debugging
  4. Allow every workload in the Kubernetes cluster to call every financial API merely because traffic stays internal

Answer & Explanations

Correct answer: B

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 university uses shared infrastructure templates containing hard-coded production API tokens. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

B.

Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. This shortcut is unsafe for: A university uses shared infrastructure templates containing hard-coded production API tokens. The resulting failure can be: Cloud environments inherit reproducible but insecure exposure across many accounts. The safer response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

C.

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 university uses shared infrastructure templates containing hard-coded production API tokens. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

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 university uses shared infrastructure templates containing hard-coded production API tokens. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

Question 535

A university uses shared infrastructure templates containing hard-coded production API tokens. Suppose the team makes this shortcut instead: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Which outcome is the most likely direct consequence?

  1. A compromised low-value service pivots to sensitive internal APIs without user-facing controls
  2. A compromised low-privilege user gains broad cloud control despite successful single sign-on enforcement
  3. Cloud environments inherit reproducible but insecure exposure across many accounts
  4. A leaked image or source bundle grants enduring privileged access across unrelated services

Answer & Explanations

Correct answer: C

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 university uses shared infrastructure templates containing hard-coded production API tokens. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

B.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

C.

Cloud environments inherit reproducible but insecure exposure across many accounts. This is the risk in the stated situation: A university uses shared infrastructure templates containing hard-coded production API tokens. The risky shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Prevent it by: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

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 university uses shared infrastructure templates containing hard-coded production API tokens. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

Question 536

A retail team distributes a Terraform module that disables audit logging for every new account. 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. Run complementary source, dependency and runtime security tests with severity-based release gates
  3. Add automated negative-path tests for cross-tenant requests, malformed tokens and privilege escalation alongside normal functional tests
  4. Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied

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 retail team distributes a Terraform module that disables audit logging for every new account. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

B.

This action is appropriate in a different case: A cloud payment API passes source checks but deploys an outdated parser with a published security issue. There, the reason is: Static analysis finds code patterns, software composition analysis checks third-party components and dynamic testing observes a deployed application's behavior. The current case is: A retail team distributes a Terraform module that disables audit logging for every new account. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

C.

This action is appropriate in a different case: A property portal's normal customer checkout succeeds but users can alter another account's billing address. There, the reason is: Functional success does not establish that unauthorized users cannot trigger the same operation through alternate inputs. The current case is: A retail team distributes a Terraform module that disables audit logging for every new account. The appropriate response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

D.

Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. The technical reason is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The stated condition is: A retail team distributes a Terraform module that disables audit logging for every new account. Confirm the result by: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

Question 537

A retail team distributes a Terraform module that disables audit logging for every new account. An engineer recommends: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. Which technical explanation most directly justifies this recommendation?

  1. Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation
  2. Functional success does not establish that unauthorized users cannot trigger the same operation through alternate inputs
  3. Dependency names and version strings alone do not prove artifacts came from the expected build pipeline or lack known severe issues
  4. TLS protects transport but cannot determine whether an authenticated caller may access a particular business object or issue excessive requests

Answer & Explanations

Correct answer: A

A.

Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. That mechanism explains the decision: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. In the reported situation: A retail team distributes a Terraform module that disables audit logging for every new account. Confirmation requires: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

B.

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 retail team distributes a Terraform module that disables audit logging for every new account. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

C.

This principle explains a different technical intervention: Require signed build artifacts, inventory of third-party dependencies and policy evaluation before deploying cloud application images. It applies to: A healthcare startup uses an unpinned container image that an unknown publisher can replace. The actual case is: A retail team distributes a Terraform module that disables audit logging for every new account. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

D.

This principle explains a different technical intervention: Enforce token validation, per-operation authorization, schema checks and rate limits at appropriate cloud API boundaries. It applies to: A retail API terminates TLS correctly but accepts any account number from a logged-in user. The actual case is: A retail team distributes a Terraform module that disables audit logging for every new account. The mechanism relevant here is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation.

Question 538

A retail team distributes a Terraform module that disables audit logging for every new account. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Use a test client to verify invalid tokens, unauthorized object IDs and over-limit calls fail with correct logged outcomes
  2. Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment
  3. Launch a test service without privileged mounts and verify it cannot access host secrets or sensitive runtime sockets
  4. Spoof a test internal caller identity and verify the target service rejects access while legitimate service requests succeed

Answer & Explanations

Correct answer: B

A.

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 retail team distributes a Terraform module that disables audit logging for every new account. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

B.

Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment. This check directly tests: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied. The underlying behavior is: Configuration is executable architecture, so insecure defaults and exposed credentials can propagate instantly through automation. The case is: A retail team distributes a Terraform module that disables audit logging for every new account.

C.

This observation would verify a different remedy: Run containers with least-privilege service identities, non-root users, read-only filesystems and explicit capability constraints where supported. That remedy applies to: A university deploys student-made web containers with access to the host container engine socket. The present condition is: A retail team distributes a Terraform module that disables audit logging for every new account. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

D.

This observation would verify a different remedy: Require authenticated service identities, appropriate mutual TLS and narrowly authorized service-to-service routes for cloud microservices. That remedy applies to: A clinic's internal appointment API trusts any caller from the cluster pod network. The present condition is: A retail team distributes a Terraform module that disables audit logging for every new account. To assess it, check: Commit a deliberately public storage rule in a test branch and confirm the CI policy prevents deployment.

Question 539

A retail team distributes a Terraform module that disables audit logging for every new account. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Allow every workload in the Kubernetes cluster to call every financial API merely because traffic stays internal
  2. Grant every federated employee global administrator privileges because the identity provider confirmed login
  3. Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review
  4. Put one production cloud administrator API key in every microservice image to make deployment easier

Answer & Explanations

Correct answer: C

A.

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 retail team distributes a Terraform module that disables audit logging for every new account. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

B.

This proposed shortcut concerns a separate case: A multinational enterprise adds SaaS login federation but accidentally maps all staff to a cloud admin group. The risk in this question concerns: A retail team distributes a Terraform module that disables audit logging for every new account. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

C.

Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. This shortcut is unsafe for: A retail team distributes a Terraform module that disables audit logging for every new account. The resulting failure can be: Cloud environments inherit reproducible but insecure exposure across many accounts. The safer response is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

D.

This proposed shortcut concerns a separate case: A bank's serverless functions all reuse a broad database administrator password stored in their source code. The risk in this question concerns: A retail team distributes a Terraform module that disables audit logging for every new account. Here the unsafe shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Use this response instead: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

Question 540

A retail team distributes a Terraform module that disables audit logging for every new account. Suppose the team makes this shortcut instead: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Which outcome is the most likely direct consequence?

  1. A leaked image or source bundle grants enduring privileged access across unrelated services
  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. Cloud environments inherit reproducible but insecure exposure across many accounts

Answer & Explanations

Correct answer: D

A.

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 retail team distributes a Terraform module that disables audit logging for every new account. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

B.

This failure concerns another scenario: A SaaS team repeatedly introduces broken object-level authorization despite enforcing user login. In the stated case: A retail team distributes a Terraform module that disables audit logging for every new account. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

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 retail team distributes a Terraform module that disables audit logging for every new account. The relevant consequence is: Cloud environments inherit reproducible but insecure exposure across many accounts. The control that prevents it is: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

D.

Cloud environments inherit reproducible but insecure exposure across many accounts. This is the risk in the stated situation: A retail team distributes a Terraform module that disables audit logging for every new account. The risky shortcut is: Embed live root credentials in a shared Terraform file and automatically apply public-firewall rules without review. Prevent it by: Enforce peer review, secret scanning and policy checks against cloud IaC changes before they are applied.

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