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 72

Question 710

A payroll SaaS meets infrastructure uptime goals but cannot complete month-end payment batches in time. Suppose the team makes this shortcut instead: Assume a provider's published 99.9-percent uptime guarantee means every tenant API meets its latency commitment. Which outcome is the most likely direct consequence?

  1. An innocuous or manipulated event causes a self-inflicted organization-wide outage
  2. Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract
  3. Instances diverge and later autoscaling recreates vulnerable or inconsistent service state
  4. Anyone who can read the logs may impersonate the signing service or undermine signatures

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A cloud SOC uses one low-confidence anomaly to revoke every production API credential in an organization. In the stated case: A payroll SaaS meets infrastructure uptime goals but cannot complete month-end payment batches in time. The relevant consequence is: Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract. The control that prevents it is: Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached.

B.

Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract. This is the risk in the stated situation: A payroll SaaS meets infrastructure uptime goals but cannot complete month-end payment batches in time. The risky shortcut is: Assume a provider's published 99.9-percent uptime guarantee means every tenant API meets its latency commitment. Prevent it by: Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached.

C.

This failure concerns another scenario: A bank autoscaling group reintroduces old vulnerable packages after engineers patch individual running instances. In the stated case: A payroll SaaS meets infrastructure uptime goals but cannot complete month-end payment batches in time. The relevant consequence is: Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract. The control that prevents it is: Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached.

D.

This failure concerns another scenario: A national archive signs compliance records but stores its only private signing key on a public web VM. In the stated case: A payroll SaaS meets infrastructure uptime goals but cannot complete month-end payment batches in time. The relevant consequence is: Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract. The control that prevents it is: Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached.

Question 711

A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Record cloud snapshot source identifiers, signed hashes, access history and transfer events through acquisition and review
  2. Build cloud worker instances from verified hardened images with constrained identity, telemetry and controlled replacement instead of unmanaged host edits
  3. Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances
  4. Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A public-sector investigator receives cloud snapshots with no timestamp or collection record. There, the reason is: An unaltered snapshot cannot be assumed trustworthy if investigators cannot show when and by whom it was captured and handled. The current case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

This action is appropriate in a different case: A bank autoscaling group reintroduces old vulnerable packages after engineers patch individual running instances. There, the reason is: Immutable deployment replaces drifted instances with approved baselines, reducing long-lived changes and unknown service configuration. The current case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. The technical reason is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. The stated condition is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Confirm the result by: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

D.

This action is appropriate in a different case: A national archive signs compliance records but stores its only private signing key on a public web VM. There, the reason is: HSM isolation reduces raw private-key exposure but still requires authorized cryptographic operations and resilient key lifecycle control. The current case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

Question 712

A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. An engineer recommends: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. Which technical explanation most directly justifies this recommendation?

  1. HSM isolation reduces raw private-key exposure but still requires authorized cryptographic operations and resilient key lifecycle control
  2. Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution
  3. Patch urgency depends on exploitability, exposure and business impact while uncontrolled simultaneous reboot can threaten service continuity
  4. Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations

Answer & Explanations

Correct answer: D

A.

This principle explains a different technical intervention: Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery. It applies to: A national archive signs compliance records but stores its only private signing key on a public web VM. The actual case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

B.

This principle explains a different technical intervention: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. It applies to: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The actual case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

C.

This principle explains a different technical intervention: Remediate critical cloud guest and container vulnerabilities using supported rollout rings with asset inventory and rollback tests. It applies to: A financial SaaS runs customer-managed web servers with a published actively exploited package vulnerability. The actual case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

D.

Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. That mechanism explains the decision: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. In the reported situation: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Confirmation requires: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

Question 713

A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation
  2. Pilot an approved update and verify vulnerable package versions are replaced without violating application SLOs
  3. Use a temporary contractor account and verify its session is logged, restricted to one host and disabled after expiry
  4. Restore a synthetic full application in isolation and verify transactions, database consistency and measured recovery time

Answer & Explanations

Correct answer: A

A.

Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation. This check directly tests: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. The underlying behavior is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. The case is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination.

B.

This observation would verify a different remedy: Remediate critical cloud guest and container vulnerabilities using supported rollout rings with asset inventory and rollback tests. That remedy applies to: A financial SaaS runs customer-managed web servers with a published actively exploited package vulnerability. The present condition is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

C.

This observation would verify a different remedy: Route remote administrative sessions through a controlled jump host with scoped roles, session recording and revocable short-lived access. That remedy applies to: A managed cloud team allows every vendor engineer to log directly into production VMs with one shared administrator key. The present condition is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

D.

This observation would verify a different remedy: Define backup schedules and recovery tests covering guest systems, configuration state and dependent cloud data stores. That remedy applies to: A hospital files nightly VM snapshots but none include the external managed database required by the application. The present condition is: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

Question 714

A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Delete the primary workload after finding green backup status without attempting any restore or checking key availability
  2. Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved
  3. Run unrestricted cloud firewall updates directly from a developer laptop without review or recovery plan
  4. Close every cloud incident after rebooting the affected VM and forbid further recurrence analysis

Answer & Explanations

Correct answer: B

A.

This proposed shortcut concerns a separate case: A hospital files nightly VM snapshots but none include the external managed database required by the application. The risk in this question concerns: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. This shortcut is unsafe for: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The resulting failure can be: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The safer response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

This proposed shortcut concerns a separate case: A retail engineer updates a shared network security template and inadvertently opens hundreds of cloud databases. The risk in this question concerns: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

D.

This proposed shortcut concerns a separate case: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. The risk in this question concerns: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

Question 715

A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. Suppose the team makes this shortcut instead: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Which outcome is the most likely direct consequence?

  1. The same root fault causes repeated outages while support metrics show superficially fast closures
  2. Customers suffer capacity-related errors even though the provider's underlying infrastructure remains within contract
  3. Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident
  4. Customers receive misleading statements and required decision-makers lose control of lawful disclosure

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. In the stated case: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

This failure concerns another scenario: A cloud university portal hits API rate limits each semester despite normal provider availability. In the stated case: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. This is the risk in the stated situation: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The risky shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Prevent it by: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

D.

This failure concerns another scenario: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. In the stated case: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

Question 716

A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery
  2. Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access
  3. Remediate critical cloud guest and container vulnerabilities using supported rollout rings with asset inventory and rollback tests
  4. Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances

Answer & Explanations

Correct answer: D

A.

This action is appropriate in a different case: A national archive signs compliance records but stores its only private signing key on a public web VM. There, the reason is: HSM isolation reduces raw private-key exposure but still requires authorized cryptographic operations and resilient key lifecycle control. The current case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

This action is appropriate in a different case: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. There, the reason is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. The current case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

This action is appropriate in a different case: A financial SaaS runs customer-managed web servers with a published actively exploited package vulnerability. There, the reason is: Patch urgency depends on exploitability, exposure and business impact while uncontrolled simultaneous reboot can threaten service continuity. The current case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The appropriate response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

D.

Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. The technical reason is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. The stated condition is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Confirm the result by: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

Question 717

A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. An engineer recommends: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. Which technical explanation most directly justifies this recommendation?

  1. Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations
  2. Patch urgency depends on exploitability, exposure and business impact while uncontrolled simultaneous reboot can threaten service continuity
  3. Remote management credentials are high impact and must be limited independently of ordinary user authentication and network reachability
  4. A backup job marked successful cannot prove restoration, encryption keys and consistent application writes are recoverable

Answer & Explanations

Correct answer: A

A.

Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. That mechanism explains the decision: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. In the reported situation: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Confirmation requires: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

B.

This principle explains a different technical intervention: Remediate critical cloud guest and container vulnerabilities using supported rollout rings with asset inventory and rollback tests. It applies to: A financial SaaS runs customer-managed web servers with a published actively exploited package vulnerability. The actual case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

C.

This principle explains a different technical intervention: Route remote administrative sessions through a controlled jump host with scoped roles, session recording and revocable short-lived access. It applies to: A managed cloud team allows every vendor engineer to log directly into production VMs with one shared administrator key. The actual case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

D.

This principle explains a different technical intervention: Define backup schedules and recovery tests covering guest systems, configuration state and dependent cloud data stores. It applies to: A hospital files nightly VM snapshots but none include the external managed database required by the application. The actual case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The mechanism relevant here is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations.

Question 718

A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Restore a synthetic full application in isolation and verify transactions, database consistency and measured recovery time
  2. Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation
  3. Submit a simulated excessive-permission change and verify the approved pipeline blocks or escalates it before apply
  4. Review a repeated outage record and confirm both service restoration timestamps and a documented permanent remediation

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Define backup schedules and recovery tests covering guest systems, configuration state and dependent cloud data stores. That remedy applies to: A hospital files nightly VM snapshots but none include the external managed database required by the application. The present condition is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

B.

Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation. This check directly tests: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. The underlying behavior is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. The case is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits.

C.

This observation would verify a different remedy: Require risk assessment, peer approval and recorded rollback for material cloud production firewall or IAM changes. That remedy applies to: A retail engineer updates a shared network security template and inadvertently opens hundreds of cloud databases. The present condition is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

D.

This observation would verify a different remedy: Use an incident process to contain service impact and a distinct problem investigation to identify and prevent recurring causes. That remedy applies to: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. The present condition is: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. To assess it, check: Reconcile memory-capture digest, timestamps, investigator rights and a read-only copy before destructive remediation.

Question 719

A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Close every cloud incident after rebooting the affected VM and forbid further recurrence analysis
  2. Assume a provider's published 99.9-percent uptime guarantee means every tenant API meets its latency commitment
  3. Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved
  4. Post unverified breach details on a public status page before security and legal teams confirm the affected data and notification obligations

Answer & Explanations

Correct answer: C

A.

This proposed shortcut concerns a separate case: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. The risk in this question concerns: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

This proposed shortcut concerns a separate case: A cloud university portal hits API rate limits each semester despite normal provider availability. The risk in this question concerns: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. This shortcut is unsafe for: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The resulting failure can be: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The safer response is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

D.

This proposed shortcut concerns a separate case: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. The risk in this question concerns: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Here the unsafe shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Use this response instead: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

Question 720

A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. Suppose the team makes this shortcut instead: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Which outcome is the most likely direct consequence?

  1. Customers receive misleading statements and required decision-makers lose control of lawful disclosure
  2. Unowned upstream faults extend service downtime while affected customers receive inconsistent updates
  3. An attacker moves between services while analysts see only disconnected partial events
  4. Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. In the stated case: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

B.

This failure concerns another scenario: A logistics company faces a regional provider DNS outage but only its internal application team is informed. In the stated case: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

C.

This failure concerns another scenario: A bank detects unusual API access after a sign-in anomaly but its identity and object logs use incompatible timestamps. In the stated case: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The relevant consequence is: Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. The control that prevents it is: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

D.

Potential attacker processes and ephemeral secrets are lost before investigators can reconstruct the incident. This is the risk in the stated situation: A medical SaaS instance is compromised and the incident team needs short-lived runtime evidence within privacy limits. The risky shortcut is: Reboot a suspected compromised cloud instance immediately and then claim its pre-reboot memory was preserved. Prevent it by: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances.

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