ISC CCSP Dumps
ISC CCSP Practice Test 2
Question 10
An education service wants to reduce overnight compute without losing headroom for morning login spikes. Suppose the team makes this shortcut instead: Reserve a fixed instance count for all future demand and describe it as automatic elastic capacity. 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: An education service wants to reduce overnight compute without losing headroom for morning login spikes. The relevant consequence is: Demand bursts exhaust service capacity and cause avoidable errors while idle periods still incur unnecessary cost. The control that prevents it is: Use monitored autoscaling limits and demand-based policies to add cloud capacity during verified workload bursts.
Demand bursts exhaust service capacity and cause avoidable errors while idle periods still incur unnecessary cost. This is the risk in the stated situation: An education service wants to reduce overnight compute without losing headroom for morning login spikes. The risky shortcut is: Reserve a fixed instance count for all future demand and describe it as automatic elastic capacity. Prevent it by: Use monitored autoscaling limits and demand-based policies to add cloud capacity during verified workload bursts.
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: An education service wants to reduce overnight compute without losing headroom for morning login spikes. The relevant consequence is: Demand bursts exhaust service capacity and cause avoidable errors while idle periods still incur unnecessary cost. The control that prevents it is: Use monitored autoscaling limits and demand-based policies to add cloud capacity during verified workload bursts.
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: An education service wants to reduce overnight compute without losing headroom for morning login spikes. The relevant consequence is: Demand bursts exhaust service capacity and cause avoidable errors while idle periods still incur unnecessary cost. The control that prevents it is: Use monitored autoscaling limits and demand-based policies to add cloud capacity during verified workload bursts.
Question 11
A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. 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 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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. The technical 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 stated condition is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Confirm the result by: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
This action is appropriate in a different case: A financial firm uses managed analytics from two providers but neither team knows how to export the audit trail. There, the reason is: Multi-cloud resilience and reversibility depend on exit-ready data and operational interfaces as well as redundant provider names. The current case is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Question 12
A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. An engineer recommends: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: D
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The mechanism relevant here 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.
This principle explains a different technical intervention: Store and rotate encryption keys in a segregated managed key service with narrowly scoped workload identities. It applies to: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. The actual case is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The mechanism relevant here 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.
This principle explains a different technical intervention: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. It applies to: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The actual case is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The mechanism relevant here 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.
IaaS shifts physical facility and underlying host duties to the provider but generally leaves guest operating systems and application access controls to the customer. That mechanism explains the decision: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. In the reported situation: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Confirmation requires: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
Question 13
A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: A
Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records. This check directly tests: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. The underlying behavior 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 case is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates.
This observation would verify a different remedy: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. That remedy applies to: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The present condition is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
This observation would verify a different remedy: Restrict hypervisor and container management APIs to dedicated privileged identities and isolated administrative paths. That remedy applies to: A hosting provider allows an internet-facing customer VLAN to reach its hypervisor management API. The present condition is: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
Question 14
A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. 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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Assume that buying IaaS means the vendor maintains every guest operating system and application account. This shortcut is unsafe for: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The resulting failure can be: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The safer response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Question 15
A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. Suppose the team makes this shortcut instead: Assume that buying IaaS means the vendor maintains every guest operating system and application account. 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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. This is the risk in the stated situation: A hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The risky shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Prevent it by: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 hospital migrates self-managed database VMs to IaaS and stops installing guest security updates. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Question 16
A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. 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 financial firm uses managed analytics from two providers but neither team knows how to export the audit trail. There, the reason is: Multi-cloud resilience and reversibility depend on exit-ready data and operational interfaces as well as redundant provider names. The current case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
This action is appropriate in a different case: A medical research team encrypts cloud objects but commits its only decryption key to the application source repository. There, the reason is: Separating key control from data storage reduces the impact of losing a storage credential and supports auditable revocation. The current case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
This action is appropriate in a different case: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. There, the reason is: Short-lived compute does not imply residual blocks and linked snapshots are purged from all relevant storage copies. The current case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The appropriate response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. The technical 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 stated condition is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Confirm the result by: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
Question 17
A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. An engineer recommends: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: A
IaaS shifts physical facility and underlying host duties to the provider but generally leaves guest operating systems and application access controls to the customer. That mechanism explains the decision: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. In the reported situation: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Confirmation requires: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
This principle explains a different technical intervention: Apply provider-supported cryptographic erase and lifecycle controls to ephemeral volumes before reassignment or final disposal. It applies to: A claims-processing batch uses temporary disks for confidential records and leaves snapshots after instance deletion. The actual case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The mechanism relevant here 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.
This principle explains a different technical intervention: Restrict hypervisor and container management APIs to dedicated privileged identities and isolated administrative paths. It applies to: A hosting provider allows an internet-facing customer VLAN to reach its hypervisor management API. The actual case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The mechanism relevant here 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.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The mechanism relevant here 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.
Question 18
A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. 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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records. This check directly tests: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider. The underlying behavior 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 case is: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. To assess it, check: Review current provider responsibility documents and show a patched guest image plus provider infrastructure assurance in separate evidence records.
Question 19
A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. 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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Assume that buying IaaS means the vendor maintains every guest operating system and application account. This shortcut is unsafe for: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The resulting failure can be: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The safer response is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Here the unsafe shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Use this response instead: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Question 20
A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. Suppose the team makes this shortcut instead: Assume that buying IaaS means the vendor maintains every guest operating system and application account. 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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
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 manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
This failure concerns another scenario: A credit union needs to relocate a regulated service between its local datacenter and a cloud without changing client interfaces. In the stated case: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The relevant consequence is: Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. The control that prevents it is: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Unpatched tenant virtual machines remain exposed while both parties incorrectly assume the other owns remediation. This is the risk in the stated situation: A manufacturer disputes responsibility after a cloud guest SSH service is compromised despite the physical hosts being provider-managed. The risky shortcut is: Assume that buying IaaS means the vendor maintains every guest operating system and application account. Prevent it by: Document an IaaS responsibility matrix assigning guest OS patching and workload identities to the customer and physical hypervisor duties to its provider.
Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests
- ISC CCSP Practice Test 1 - 10 Questions (Last Reviewed 19-Nov-2026)
- ISC CCSP Practice Test 2 - 10 Questions (Last Reviewed 18-Nov-2026)
- ISC CCSP Practice Test 3 - 10 Questions (Last Reviewed 17-Nov-2026)
- ISC CCSP Practice Test 4 - 10 Questions (Last Reviewed 16-Nov-2026)