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 7

Question 60

A publisher's subscription provider announces termination while the customer has no validated customer-data export path. Suppose the team makes this shortcut instead: Rely on marketing claims of multi-cloud portability without testing full data export or dependency migration. Which outcome is the most likely direct consequence?

  1. Demand bursts exhaust service capacity and cause avoidable errors while idle periods still incur unnecessary cost
  2. Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation
  3. One tenant retrieves another tenant's records despite normal appearance of the shared cloud portal
  4. The organization cannot leave the provider within its contract window or validate that records were transferred intact

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A regional ticketing portal receives unpredictable concert-release surges and repeatedly reaches its fixed instance limit. In the stated case: A publisher's subscription provider announces termination while the customer has no validated customer-data export path. The relevant consequence is: The organization cannot leave the provider within its contract window or validate that records were transferred intact. The control that prevents it is: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service.

B.

This failure concerns another scenario: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. In the stated case: A publisher's subscription provider announces termination while the customer has no validated customer-data export path. The relevant consequence is: The organization cannot leave the provider within its contract window or validate that records were transferred intact. The control that prevents it is: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service.

C.

This failure concerns another scenario: A SaaS analytics provider separates customers with labels but has never tested object-level access between their APIs. In the stated case: A publisher's subscription provider announces termination while the customer has no validated customer-data export path. The relevant consequence is: The organization cannot leave the provider within its contract window or validate that records were transferred intact. The control that prevents it is: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service.

D.

The organization cannot leave the provider within its contract window or validate that records were transferred intact. This is the risk in the stated situation: A publisher's subscription provider announces termination while the customer has no validated customer-data export path. The risky shortcut is: Rely on marketing claims of multi-cloud portability without testing full data export or dependency migration. Prevent it by: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service.

Question 61

A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities
  2. Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal
  3. Restrict hypervisor and container management APIs to dedicated privileged identities and isolated administrative paths
  4. Use monitored autoscaling limits and demand-based policies to add cloud capacity during verified workload bursts

Answer & Explanations

Correct answer: A

A.

Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. The technical reason is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. The stated condition is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Confirm the result by: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

B.

This action is appropriate in a different case: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. There, the reason is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The current case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

C.

This action is appropriate in a different case: A hosting provider allows an internet-facing customer VLAN to reach its hypervisor management API. There, the reason is: Compromise of the virtualization management plane can undermine the isolation of many guest workloads at once. The current case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

This action is appropriate in a different case: A regional ticketing portal receives unpredictable concert-release surges and repeatedly reaches its fixed instance limit. There, the reason is: Rapid elasticity adjusts provisioned resources as demand changes while a static capacity plan cannot follow short unpredictable peaks. The current case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

Question 62

A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. An engineer recommends: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. Which technical explanation most directly justifies this recommendation?

  1. Compromise of the virtualization management plane can undermine the isolation of many guest workloads at once
  2. Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation
  3. IaaS shifts physical facility and underlying host duties to the provider but generally leaves guest operating systems and application access controls to the customer
  4. Resource pooling and multi-tenancy do not guarantee that application credentials or virtual network policies separate customers correctly

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Restrict hypervisor and container management APIs to dedicated privileged identities and isolated administrative paths. It applies to: A hosting provider allows an internet-facing customer VLAN to reach its hypervisor management API. The actual case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

B.

Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. That mechanism explains the decision: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. In the reported situation: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Confirmation requires: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

C.

This principle explains a different technical intervention: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. It applies to: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The actual case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

D.

This principle explains a different technical intervention: Establish separate tenant identities, network boundaries and resource policies with negative authorization tests for a pooled cloud deployment. It applies to: A SaaS analytics provider separates customers with labels but has never tested object-level access between their APIs. The actual case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

Question 63

A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Test an authenticated tenant A principal against tenant B resources and confirm access is denied and logged
  2. Relocate a representative workload and its data in a pilot and verify identity, performance and application transactions at the alternate site
  3. Revoke a test workload grant and confirm access fails while permitted service identities still decrypt
  4. Compare provider control evidence with customer-required OS, runtime and application duties in a signed responsibility mapping

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Establish separate tenant identities, network boundaries and resource policies with negative authorization tests for a pooled cloud deployment. That remedy applies to: A SaaS analytics provider separates customers with labels but has never tested object-level access between their APIs. The present condition is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

B.

This observation would verify a different remedy: Design a hybrid deployment around compatible interfaces, documented connectivity and a tested workload return path. That remedy applies to: A credit union needs to relocate a regulated service between its local datacenter and a cloud without changing client interfaces. The present condition is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

C.

Revoke a test workload grant and confirm access fails while permitted service identities still decrypt. This check directly tests: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. The underlying behavior is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. The case is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository.

D.

This observation would verify a different remedy: Select a cloud service category according to who must manage runtime, patching and application configuration. That remedy applies to: A medical device vendor needs custom kernel monitoring that is not exposed by an offered SaaS application. The present condition is: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

Question 64

A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Choose SaaS for an application that explicitly requires installing custom kernel modules inside a customer-managed guest
  2. Rely on marketing claims of multi-cloud portability without testing full data export or dependency migration
  3. Promise zero data loss using one nightly asynchronous backup without assessing business transaction frequency
  4. Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A medical device vendor needs custom kernel monitoring that is not exposed by an offered SaaS application. The risk in this question concerns: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

B.

This proposed shortcut concerns a separate case: A financial firm uses managed analytics from two providers but neither team knows how to export the audit trail. The risk in this question concerns: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

C.

This proposed shortcut concerns a separate case: A bank processes orders continuously but uses a nightly backup despite a fifteen-minute data-loss requirement. The risk in this question concerns: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. This shortcut is unsafe for: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The resulting failure can be: A repository compromise exposes both protected data and the key material needed to decrypt it. The safer response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

Question 65

A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. Suppose the team makes this shortcut instead: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Which outcome is the most likely direct consequence?

  1. A repository compromise exposes both protected data and the key material needed to decrypt it
  2. A platform outage results in greater data loss or restoration delay than business owners accepted
  3. Misconfigured public resources and missing audit evidence proliferate across independently created accounts
  4. The buyer relies on assurance that excludes its actual workloads and cannot demonstrate required controls to auditors

Answer & Explanations

Correct answer: A

A.

A repository compromise exposes both protected data and the key material needed to decrypt it. This is the risk in the stated situation: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The risky shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Prevent it by: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

B.

This failure concerns another scenario: A bank processes orders continuously but uses a nightly backup despite a fifteen-minute data-loss requirement. In the stated case: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

C.

This failure concerns another scenario: A regional insurer opens dozens of new cloud subscriptions without consistent logging or baseline network policy. In the stated case: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

This failure concerns another scenario: An insurer selects a regional backup service based on a SOC report covering only the provider's office IT. In the stated case: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

Question 66

A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Restrict hypervisor and container management APIs to dedicated privileged identities and isolated administrative paths
  2. Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities
  3. Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider
  4. Establish separate tenant identities, network boundaries and resource policies with negative authorization tests for a pooled cloud deployment

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A hosting provider allows an internet-facing customer VLAN to reach its hypervisor management API. There, the reason is: Compromise of the virtualization management plane can undermine the isolation of many guest workloads at once. The current case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

B.

Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. The technical reason is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. The stated condition is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Confirm the result by: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

C.

This action is appropriate in a different case: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. There, the reason is: IaaS shifts physical facility and underlying host duties to the provider but generally leaves guest operating systems and application access controls to the customer. The current case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

This action is appropriate in a different case: A SaaS analytics provider separates customers with labels but has never tested object-level access between their APIs. There, the reason is: Resource pooling and multi-tenancy do not guarantee that application credentials or virtual network policies separate customers correctly. The current case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The appropriate response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

Question 67

A payment service needs to revoke one workload's key access without affecting unrelated billing applications. An engineer recommends: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. Which technical explanation most directly justifies this recommendation?

  1. Resource pooling and multi-tenancy do not guarantee that application credentials or virtual network policies separate customers correctly
  2. Portability depends on application interfaces, data formats and control-plane dependencies rather than the mere presence of two clouds
  3. Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation
  4. SaaS abstracts most application operations, PaaS abstracts the runtime platform, and IaaS exposes more operating-system and infrastructure choices

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Establish separate tenant identities, network boundaries and resource policies with negative authorization tests for a pooled cloud deployment. It applies to: A SaaS analytics provider separates customers with labels but has never tested object-level access between their APIs. The actual case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

B.

This principle explains a different technical intervention: Design a hybrid deployment around compatible interfaces, documented connectivity and a tested workload return path. It applies to: A credit union needs to relocate a regulated service between its local datacenter and a cloud without changing client interfaces. The actual case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

C.

Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. That mechanism explains the decision: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. In the reported situation: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Confirmation requires: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

D.

This principle explains a different technical intervention: Select a cloud service category according to who must manage runtime, patching and application configuration. It applies to: A medical device vendor needs custom kernel monitoring that is not exposed by an offered SaaS application. The actual case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The mechanism relevant here is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation.

Question 68

A payment service needs to revoke one workload's key access without affecting unrelated billing applications. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Compare provider control evidence with customer-required OS, runtime and application duties in a signed responsibility mapping
  2. Perform a timed export and import pilot into an independent environment and reconcile record counts and checksums
  3. Execute a simulated incident and compare actual restored timestamps and elapsed service downtime with approved targets
  4. Revoke a test workload grant and confirm access fails while permitted service identities still decrypt

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Select a cloud service category according to who must manage runtime, patching and application configuration. That remedy applies to: A medical device vendor needs custom kernel monitoring that is not exposed by an offered SaaS application. The present condition is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

B.

This observation would verify a different remedy: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service. That remedy applies to: A financial firm uses managed analytics from two providers but neither team knows how to export the audit trail. The present condition is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

C.

This observation would verify a different remedy: Set tier-specific recovery time and recovery point requirements from business impact analysis before choosing replication and backup schedules. That remedy applies to: A bank processes orders continuously but uses a nightly backup despite a fifteen-minute data-loss requirement. The present condition is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. To assess it, check: Revoke a test workload grant and confirm access fails while permitted service identities still decrypt.

D.

Revoke a test workload grant and confirm access fails while permitted service identities still decrypt. This check directly tests: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. The underlying behavior is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. The case is: A payment service needs to revoke one workload's key access without affecting unrelated billing applications.

Question 69

A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset
  2. Promise zero data loss using one nightly asynchronous backup without assessing business transaction frequency
  3. Let every development team build production cloud accounts without centralized identity, logging or allowed-region controls
  4. Assume a provider's corporate SOC report proves that an unrelated newly purchased AI service is in scope

Answer & Explanations

Correct answer: A

A.

Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. This shortcut is unsafe for: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The resulting failure can be: A repository compromise exposes both protected data and the key material needed to decrypt it. The safer response is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

B.

This proposed shortcut concerns a separate case: A bank processes orders continuously but uses a nightly backup despite a fifteen-minute data-loss requirement. The risk in this question concerns: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

C.

This proposed shortcut concerns a separate case: A regional insurer opens dozens of new cloud subscriptions without consistent logging or baseline network policy. The risk in this question concerns: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

This proposed shortcut concerns a separate case: An insurer selects a regional backup service based on a SOC report covering only the provider's office IT. The risk in this question concerns: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Here the unsafe shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Use this response instead: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

Question 70

A payment service needs to revoke one workload's key access without affecting unrelated billing applications. Suppose the team makes this shortcut instead: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Which outcome is the most likely direct consequence?

  1. The buyer relies on assurance that excludes its actual workloads and cannot demonstrate required controls to auditors
  2. A repository compromise exposes both protected data and the key material needed to decrypt it
  3. A procurement attestation overstates technical assurance and protected workloads may use an unvalidated cryptographic implementation
  4. Sensitive records can be leaked through model behavior or malicious samples can degrade security decisions

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: An insurer selects a regional backup service based on a SOC report covering only the provider's office IT. In the stated case: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

B.

A repository compromise exposes both protected data and the key material needed to decrypt it. This is the risk in the stated situation: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The risky shortcut is: Store encryption keys in the same publicly reachable configuration repository as the encrypted dataset. Prevent it by: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

C.

This failure concerns another scenario: A public agency requires validated encryption but the chosen cloud service refers only to a different certified product version. In the stated case: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

D.

This failure concerns another scenario: An online retailer combines third-party training records with private customer records without documenting their source. In the stated case: A payment service needs to revoke one workload's key access without affecting unrelated billing applications. The relevant consequence is: A repository compromise exposes both protected data and the key material needed to decrypt it. The control that prevents it is: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities.

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