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 85

Question 840

A municipal cloud buyer sees a SOC 2 logo but the audited system excludes its chosen managed AI service. Suppose the team makes this shortcut instead: Treat an outdated SOC 2 report for a vendor's payroll system as proof its new cloud database product was audited. Which outcome is the most likely direct consequence?

  1. A major incident exposes missing evidence and unworkable supplier cooperation when legal deadlines apply
  2. Undisclosed international transfers create legal and contractual exposure when processing falls outside approved jurisdictions
  3. Relevant evidence becomes inadmissible or privacy rights are infringed through overbroad collection
  4. A procurement or audit decision relies on assurance outside the purchased service and reporting period

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A healthcare organization needs contractual access to incident logs from a managed cloud service that holds patient information. In the stated case: A municipal cloud buyer sees a SOC 2 logo but the audited system excludes its chosen managed AI service. The relevant consequence is: A procurement or audit decision relies on assurance outside the purchased service and reporting period. The control that prevents it is: Evaluate SOC 2 Type 2 or equivalent reports for stated control period, service boundaries, exceptions and complementary user entity controls.

B.

This failure concerns another scenario: A financial institution stores customer data locally but support logs are processed by an overseas subcontractor. In the stated case: A municipal cloud buyer sees a SOC 2 logo but the audited system excludes its chosen managed AI service. The relevant consequence is: A procurement or audit decision relies on assurance outside the purchased service and reporting period. The control that prevents it is: Evaluate SOC 2 Type 2 or equivalent reports for stated control period, service boundaries, exceptions and complementary user entity controls.

C.

This failure concerns another scenario: A multinational firm receives a lawful litigation request covering collaborative SaaS chats and selected object-storage records. In the stated case: A municipal cloud buyer sees a SOC 2 logo but the audited system excludes its chosen managed AI service. The relevant consequence is: A procurement or audit decision relies on assurance outside the purchased service and reporting period. The control that prevents it is: Evaluate SOC 2 Type 2 or equivalent reports for stated control period, service boundaries, exceptions and complementary user entity controls.

D.

A procurement or audit decision relies on assurance outside the purchased service and reporting period. This is the risk in the stated situation: A municipal cloud buyer sees a SOC 2 logo but the audited system excludes its chosen managed AI service. The risky shortcut is: Treat an outdated SOC 2 report for a vendor's payroll system as proof its new cloud database product was audited. Prevent it by: Evaluate SOC 2 Type 2 or equivalent reports for stated control period, service boundaries, exceptions and complementary user entity controls.

Question 841

An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time
  2. Coordinate eDiscovery collection across provider logs, SaaS records and tenant storage with scoped legal holds and defensible custody
  3. Document who determines personal-data purposes and means versus who processes records on behalf of another party for a specific cloud service
  4. Conduct a proportional privacy impact assessment identifying data subjects, purpose, risks, mitigations and accountable approval for new sensitive cloud processing

Answer & Explanations

Correct answer: A

A.

Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. The technical reason is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. The stated condition is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Confirm the result by: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

B.

This action is appropriate in a different case: A multinational firm receives a lawful litigation request covering collaborative SaaS chats and selected object-storage records. There, the reason is: Legal evidence can be dispersed among providers, and uncontrolled deletion or export can destroy integrity or exceed lawful collection authority. The current case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

C.

This action is appropriate in a different case: A health benefits company decides why member data is collected while a SaaS provider hosts it under instructions. There, the reason is: Privacy roles follow actual decision authority and contractual processing instructions rather than vendor or tenant branding. The current case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

This action is appropriate in a different case: A health insurer wants to combine medical and location data for an automated risk score. There, the reason is: Technical encryption alone does not establish necessity, lawful basis or proportionality of personal-data use. The current case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

Question 842

An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. An engineer recommends: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. Which technical explanation most directly justifies this recommendation?

  1. Technical encryption alone does not establish necessity, lawful basis or proportionality of personal-data use
  2. Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations
  3. Keeping unnecessary personal data increases breach impact and impairs the ability to meet applicable privacy requests
  4. Risk treatment options have different effects; a transferred financial loss does not remove operational or regulatory obligations

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Conduct a proportional privacy impact assessment identifying data subjects, purpose, risks, mitigations and accountable approval for new sensitive cloud processing. It applies to: A health insurer wants to combine medical and location data for an automated risk score. The actual case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

B.

Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. That mechanism explains the decision: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. In the reported situation: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Confirmation requires: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

C.

This principle explains a different technical intervention: Limit collected identifiers to an approved purpose and design verifiable correction, access and deletion workflows subject to lawful retention exceptions. It applies to: A delivery app asks customers for a complete national ID number although shipment pickup needs only an address. The actual case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

D.

This principle explains a different technical intervention: Record assessed cloud risk, candidate controls, expected residual impact and authorized treatment as avoid, mitigate, transfer or accept. It applies to: A startup considers accepting a low-impact regional outage but has no documented risk owner. The actual case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

Question 843

An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Review a sample risk decision for owner approval, control evidence, residual risk value and defined reassessment trigger
  2. Review a proposed dataset sharing request and verify the accountable owner approved it before custodians change access
  3. Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence
  4. Reassess a vendor after an announced service architecture change and confirm updated scope, controls and residual-risk decision

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Record assessed cloud risk, candidate controls, expected residual impact and authorized treatment as avoid, mitigate, transfer or accept. That remedy applies to: A startup considers accepting a low-impact regional outage but has no documented risk owner. The present condition is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

B.

This observation would verify a different remedy: Assign a data owner or controller to authorized purpose and policy decisions while service custodians implement defined technical controls. That remedy applies to: A bank's cloud administrator can set bucket ACLs but has no mandate to approve public use of customer credit records. The present condition is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

C.

Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence. This check directly tests: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. The underlying behavior is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. The case is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments.

D.

This observation would verify a different remedy: Review cloud vendor risk using assurance exceptions, dependency mapping, incident trend and agreed measurable control indicators. That remedy applies to: A finance platform's SaaS provider outsources identity management to an unfamiliar subcontractor. The present condition is: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

Question 844

An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Approve a critical new subcontractor without due diligence because the primary supplier was certified five years ago
  2. Assume the customer can always leave instantly because the vendor provides a generic cancel-subscription button
  3. Sign a contract containing only an uptime percentage while assuming full forensic logs and audit rights will be available on request
  4. Audit only currently running VMs and conclude that all short-lived production workloads were covered

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A finance platform's SaaS provider outsources identity management to an unfamiliar subcontractor. The risk in this question concerns: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

B.

This proposed shortcut concerns a separate case: An insurer changes customer-support SaaS vendors but its agreement never specifies structured export or deletion evidence. The risk in this question concerns: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

C.

This proposed shortcut concerns a separate case: A healthcare organization needs contractual access to incident logs from a managed cloud service that holds patient information. The risk in this question concerns: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

Audit only currently running VMs and conclude that all short-lived production workloads were covered. This shortcut is unsafe for: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The resulting failure can be: Unrecorded transient compute and configuration drift evade required assurance controls. The safer response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

Question 845

An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. Suppose the team makes this shortcut instead: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Which outcome is the most likely direct consequence?

  1. Unrecorded transient compute and configuration drift evade required assurance controls
  2. A major incident exposes missing evidence and unworkable supplier cooperation when legal deadlines apply
  3. Undisclosed international transfers create legal and contractual exposure when processing falls outside approved jurisdictions
  4. Relevant evidence becomes inadmissible or privacy rights are infringed through overbroad collection

Answer & Explanations

Correct answer: A

A.

Unrecorded transient compute and configuration drift evade required assurance controls. This is the risk in the stated situation: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The risky shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Prevent it by: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

B.

This failure concerns another scenario: A healthcare organization needs contractual access to incident logs from a managed cloud service that holds patient information. In the stated case: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

C.

This failure concerns another scenario: A financial institution stores customer data locally but support logs are processed by an overseas subcontractor. In the stated case: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

This failure concerns another scenario: A multinational firm receives a lawful litigation request covering collaborative SaaS chats and selected object-storage records. In the stated case: An audit team finds no running risky containers but production logs show hundreds of short-lived deployments. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

Question 846

A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Conduct a proportional privacy impact assessment identifying data subjects, purpose, risks, mitigations and accountable approval for new sensitive cloud processing
  2. Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time
  3. Limit collected identifiers to an approved purpose and design verifiable correction, access and deletion workflows subject to lawful retention exceptions
  4. Record assessed cloud risk, candidate controls, expected residual impact and authorized treatment as avoid, mitigate, transfer or accept

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A health insurer wants to combine medical and location data for an automated risk score. There, the reason is: Technical encryption alone does not establish necessity, lawful basis or proportionality of personal-data use. The current case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

B.

Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. The technical reason is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. The stated condition is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Confirm the result by: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

C.

This action is appropriate in a different case: A delivery app asks customers for a complete national ID number although shipment pickup needs only an address. There, the reason is: Keeping unnecessary personal data increases breach impact and impairs the ability to meet applicable privacy requests. The current case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

This action is appropriate in a different case: A startup considers accepting a low-impact regional outage but has no documented risk owner. There, the reason is: Risk treatment options have different effects; a transferred financial loss does not remove operational or regulatory obligations. The current case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The appropriate response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

Question 847

A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. An engineer recommends: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. Which technical explanation most directly justifies this recommendation?

  1. Risk treatment options have different effects; a transferred financial loss does not remove operational or regulatory obligations
  2. Cloud service operators and custodians can administer storage without inherently owning legal or business choices about sensitive data use
  3. Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations
  4. A supplier's historic accreditation is a starting point, not proof that new services and subprocessor changes remain within the same risk envelope

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Record assessed cloud risk, candidate controls, expected residual impact and authorized treatment as avoid, mitigate, transfer or accept. It applies to: A startup considers accepting a low-impact regional outage but has no documented risk owner. The actual case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

B.

This principle explains a different technical intervention: Assign a data owner or controller to authorized purpose and policy decisions while service custodians implement defined technical controls. It applies to: A bank's cloud administrator can set bucket ACLs but has no mandate to approve public use of customer credit records. The actual case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

C.

Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. That mechanism explains the decision: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. In the reported situation: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Confirmation requires: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

D.

This principle explains a different technical intervention: Review cloud vendor risk using assurance exceptions, dependency mapping, incident trend and agreed measurable control indicators. It applies to: A finance platform's SaaS provider outsources identity management to an unfamiliar subcontractor. The actual case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The mechanism relevant here is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations.

Question 848

A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Reassess a vendor after an announced service architecture change and confirm updated scope, controls and residual-risk decision
  2. Conduct a mock export and compare results with contract acceptance criteria and tested recovery procedures
  3. Review a sample serious-incident response and verify contractually promised notice timing, log access and accountable escalation
  4. Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Review cloud vendor risk using assurance exceptions, dependency mapping, incident trend and agreed measurable control indicators. That remedy applies to: A finance platform's SaaS provider outsources identity management to an unfamiliar subcontractor. The present condition is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

B.

This observation would verify a different remedy: Require clear data export format, deletion confirmation, service exit assistance and transition windows in cloud outsourcing contracts. That remedy applies to: An insurer changes customer-support SaaS vendors but its agreement never specifies structured export or deletion evidence. The present condition is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

C.

This observation would verify a different remedy: Include incident notification, subprocessor transparency, evidence access and audit scope in negotiated cloud service agreements. That remedy applies to: A healthcare organization needs contractual access to incident logs from a managed cloud service that holds patient information. The present condition is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. To assess it, check: Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence.

D.

Reconstruct a representative deployment at a past timestamp and reconcile its template, approvals and runtime evidence. This check directly tests: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time. The underlying behavior is: Traditional point-in-time server inventories miss ephemeral resources created and destroyed between audit observations. The case is: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter.

Question 849

A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Audit only currently running VMs and conclude that all short-lived production workloads were covered
  2. Sign a contract containing only an uptime percentage while assuming full forensic logs and audit rights will be available on request
  3. Assume every data processing operation remains domestic because the primary database is located in a local cloud region
  4. Perform ad hoc searches of every employee's private cloud account without authorization and overwrite originals during export

Answer & Explanations

Correct answer: A

A.

Audit only currently running VMs and conclude that all short-lived production workloads were covered. This shortcut is unsafe for: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The resulting failure can be: Unrecorded transient compute and configuration drift evade required assurance controls. The safer response is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

B.

This proposed shortcut concerns a separate case: A healthcare organization needs contractual access to incident logs from a managed cloud service that holds patient information. The risk in this question concerns: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

C.

This proposed shortcut concerns a separate case: A financial institution stores customer data locally but support logs are processed by an overseas subcontractor. The risk in this question concerns: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

This proposed shortcut concerns a separate case: A multinational firm receives a lawful litigation request covering collaborative SaaS chats and selected object-storage records. The risk in this question concerns: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Here the unsafe shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Use this response instead: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

Question 850

A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. Suppose the team makes this shortcut instead: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Which outcome is the most likely direct consequence?

  1. Relevant evidence becomes inadmissible or privacy rights are infringed through overbroad collection
  2. Unrecorded transient compute and configuration drift evade required assurance controls
  3. Accountability and data-subject obligations are assigned incorrectly and processing lacks proper instructions
  4. Sensitive automated processing proceeds without assessing rights impact or acceptable collection practices

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A multinational firm receives a lawful litigation request covering collaborative SaaS chats and selected object-storage records. In the stated case: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

B.

Unrecorded transient compute and configuration drift evade required assurance controls. This is the risk in the stated situation: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The risky shortcut is: Audit only currently running VMs and conclude that all short-lived production workloads were covered. Prevent it by: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

C.

This failure concerns another scenario: A health benefits company decides why member data is collected while a SaaS provider hosts it under instructions. In the stated case: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

D.

This failure concerns another scenario: A health insurer wants to combine medical and location data for an automated risk score. In the stated case: A payment SaaS security audit needs evidence of all infrastructure changes during the previous quarter. The relevant consequence is: Unrecorded transient compute and configuration drift evade required assurance controls. The control that prevents it is: Use cloud API inventories and signed deployment logs to sample temporary containers and infrastructure-as-code changes across time.

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