ISC CCSP Dumps
ISC CCSP Practice Test 8
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?
Answer & Explanations
Correct answer: B
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.
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.
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.
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.
Question 71
A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: 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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. The technical reason is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The stated condition is: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Confirm the result by: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Question 72
A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. An engineer recommends: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: 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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. That mechanism explains the decision: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. In the reported situation: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Confirmation requires: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
Question 73
A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: A
Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence. This check directly tests: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. The underlying behavior is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The case is: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
Question 74
A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: 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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. This shortcut is unsafe for: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The resulting failure can be: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The safer response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Question 75
A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. Suppose the team makes this shortcut instead: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: C
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Sensitive records survive in orphaned copies outside the visible virtual machine inventory. This is the risk in the stated situation: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The risky shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Prevent it by: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Question 76
A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: 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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
This action is appropriate in a different case: A credit union needs to relocate a regulated service between its local datacenter and a cloud without changing client interfaces. There, the reason is: Portability depends on application interfaces, data formats and control-plane dependencies rather than the mere presence of two clouds. The current case is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
This action is appropriate in a different case: A medical device vendor needs custom kernel monitoring that is not exposed by an offered SaaS application. There, the reason is: SaaS abstracts most application operations, PaaS abstracts the runtime platform, and IaaS exposes more operating-system and infrastructure choices. The current case is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The appropriate response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. The technical reason is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The stated condition is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Confirm the result by: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
Question 77
A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. An engineer recommends: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: A
Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. That mechanism explains the decision: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. In the reported situation: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Confirmation requires: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
This principle explains a different technical intervention: Define data export format, integrity checks, identity migration and contractual deletion evidence before adopting a proprietary managed cloud service. It applies to: A financial firm uses managed analytics from two providers but neither team knows how to export the audit trail. The actual case is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
This principle explains a different technical intervention: Set tier-specific recovery time and recovery point requirements from business impact analysis before choosing replication and backup schedules. It applies to: A bank processes orders continuously but uses a nightly backup despite a fifteen-minute data-loss requirement. The actual case is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The mechanism relevant here is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies.
Question 78
A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: B
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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence. This check directly tests: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. The underlying behavior is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The case is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal.
This observation would verify a different remedy: Create a governed cloud landing zone with baseline identities, logging, network boundaries and policy-as-code before provisioning business workloads. That remedy applies to: A regional insurer opens dozens of new cloud subscriptions without consistent logging or baseline network policy. The present condition is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
This observation would verify a different remedy: Evaluate the provider's current independent assurance report against the purchased service, geographic region, report period and customer-control exceptions. That remedy applies to: An insurer selects a regional backup service based on a SOC report covering only the provider's office IT. The present condition is: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. To assess it, check: Terminate a test workload and inspect provider deletion status, associated snapshots and audited cryptographic-key destruction evidence.
Question 79
A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: C
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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
This proposed shortcut concerns a separate case: A public agency requires validated encryption but the chosen cloud service refers only to a different certified product version. The risk in this question concerns: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. This shortcut is unsafe for: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The resulting failure can be: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The safer response is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
This proposed shortcut concerns a separate case: An online retailer combines third-party training records with private customer records without documenting their source. The risk in this question concerns: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Here the unsafe shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Use this response instead: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Question 80
A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. Suppose the team makes this shortcut instead: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: 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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
This failure concerns another scenario: A cloud SOC wants an AI classifier to isolate every VM tagged suspicious even when the alert is uncorroborated. In the stated case: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
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 research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The relevant consequence is: Sensitive records survive in orphaned copies outside the visible virtual machine inventory. The control that prevents it is: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Sensitive records survive in orphaned copies outside the visible virtual machine inventory. This is the risk in the stated situation: A research tenant decommissions project storage but an encrypted backup remains readable to an old service principal. The risky shortcut is: Assume deleting a VM reference instantly destroys every persistent disk, image, snapshot and decryption key. Prevent it by: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal.
Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests
- ISC CCSP Practice Test 6 - 10 Questions (Last Reviewed 14-Nov-2026)
- ISC CCSP Practice Test 7 - 10 Questions (Last Reviewed 13-Nov-2026)
- ISC CCSP Practice Test 8 - 10 Questions (Last Reviewed 12-Nov-2026)
- ISC CCSP Practice Test 9 - 10 Questions (Last Reviewed 11-Nov-2026)
- ISC CCSP Practice Test 10 - 10 Questions (Last Reviewed 10-Nov-2026)