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 65

Question 640

A payment processor wants isolated cryptographic signing even when application servers are compromised. Suppose the team makes this shortcut instead: Copy a highly sensitive private signing key into ordinary application debug logs to make rotations easier. Which outcome is the most likely direct consequence?

  1. An attacker moves between services while analysts see only disconnected partial events
  2. Shared infrastructure or third-party tenants suffer disruption and testing violates contractual restrictions
  3. An innocuous or manipulated event causes a self-inflicted organization-wide outage
  4. Anyone who can read the logs may impersonate the signing service or undermine signatures

Answer & Explanations

Correct answer: D

A.

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 payment processor wants isolated cryptographic signing even when application servers are compromised. The relevant consequence is: Anyone who can read the logs may impersonate the signing service or undermine signatures. The control that prevents it is: Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery.

B.

This failure concerns another scenario: A research SaaS team wants to stress-test a managed database endpoint shared with other tenants. In the stated case: A payment processor wants isolated cryptographic signing even when application servers are compromised. The relevant consequence is: Anyone who can read the logs may impersonate the signing service or undermine signatures. The control that prevents it is: Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery.

C.

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 payment processor wants isolated cryptographic signing even when application servers are compromised. The relevant consequence is: Anyone who can read the logs may impersonate the signing service or undermine signatures. The control that prevents it is: Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery.

D.

Anyone who can read the logs may impersonate the signing service or undermine signatures. This is the risk in the stated situation: A payment processor wants isolated cryptographic signing even when application servers are compromised. The risky shortcut is: Copy a highly sensitive private signing key into ordinary application debug logs to make rotations easier. Prevent it by: Select a supported HSM-backed key service for high-assurance signing keys with segregated administrators and documented recovery.

Question 641

A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access
  2. Define backup schedules and recovery tests covering guest systems, configuration state and dependent cloud data stores
  3. Require risk assessment, peer approval and recorded rollback for material cloud production firewall or IAM changes
  4. Use an incident process to contain service impact and a distinct problem investigation to identify and prevent recurring causes

Answer & Explanations

Correct answer: A

A.

Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. The technical reason is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. The stated condition is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Confirm the result by: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

B.

This action is appropriate in a different case: A hospital files nightly VM snapshots but none include the external managed database required by the application. There, the reason is: A backup job marked successful cannot prove restoration, encryption keys and consistent application writes are recoverable. The current case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

C.

This action is appropriate in a different case: A retail engineer updates a shared network security template and inadvertently opens hundreds of cloud databases. There, the reason is: Infrastructure-as-code speeds deployment but an incorrect policy can affect many resources at once unless changes are scoped and reviewed. The current case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

This action is appropriate in a different case: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. There, the reason is: Restoring service quickly does not explain why the fault occurred, and a separate cause analysis is needed for durable corrective controls. The current case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

Question 642

A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. An engineer recommends: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. Which technical explanation most directly justifies this recommendation?

  1. Restoring service quickly does not explain why the fault occurred, and a separate cause analysis is needed for durable corrective controls
  2. Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution
  3. Provider uptime targets do not ensure an application's end-to-end availability when its own quotas, queues or storage are exhausted
  4. Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Use an incident process to contain service impact and a distinct problem investigation to identify and prevent recurring causes. It applies to: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. The actual case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

B.

Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. That mechanism explains the decision: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. In the reported situation: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Confirmation requires: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

C.

This principle explains a different technical intervention: Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached. It applies to: A cloud university portal hits API rate limits each semester despite normal provider availability. The actual case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

D.

This principle explains a different technical intervention: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. It applies to: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The actual case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

Question 643

A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. 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. Recompute evidence checksums after transfer and match them to the immutable collection manifest and custody log
  3. Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA
  4. Simulate a high-severity incident and confirm the right legal, business and supplier contacts receive approved updates within applicable deadlines

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. That remedy applies to: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The present condition is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

B.

This observation would verify a different remedy: Record cloud snapshot source identifiers, signed hashes, access history and transfer events through acquisition and review. That remedy applies to: A public-sector investigator receives cloud snapshots with no timestamp or collection record. The present condition is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

C.

Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA. This check directly tests: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. The underlying behavior is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. The case is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud.

D.

This observation would verify a different remedy: Use an incident communication matrix that maps severity, contractual notice duties and regulatory decision owners to approved factual updates. That remedy applies to: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. The present condition is: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

Question 644

A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Post unverified breach details on a public status page before security and legal teams confirm the affected data and notification obligations
  2. Assume every third-party outage can be solved by rebooting tenant resources without contacting the responsible provider
  3. Keep each cloud account's raw security logs in short-lived local buffers with no central analysis
  4. Expose all cloud control consoles on unrestricted public IP addresses for operational convenience

Answer & Explanations

Correct answer: D

A.

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 university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

B.

This proposed shortcut concerns a separate case: A logistics company faces a regional provider DNS outage but only its internal application team is informed. The risk in this question concerns: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

C.

This proposed shortcut concerns a separate case: A bank detects unusual API access after a sign-in anomaly but its identity and object logs use incompatible timestamps. The risk in this question concerns: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. This shortcut is unsafe for: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The resulting failure can be: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The safer response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

Question 645

A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. Suppose the team makes this shortcut instead: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Which outcome is the most likely direct consequence?

  1. An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account
  2. An attacker moves between services while analysts see only disconnected partial events
  3. Shared infrastructure or third-party tenants suffer disruption and testing violates contractual restrictions
  4. An innocuous or manipulated event causes a self-inflicted organization-wide outage

Answer & Explanations

Correct answer: A

A.

An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. This is the risk in the stated situation: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The risky shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Prevent it by: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

B.

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 university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

C.

This failure concerns another scenario: A research SaaS team wants to stress-test a managed database endpoint shared with other tenants. In the stated case: A university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

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 university exposes hypervisor consoles directly to the internet after migrating systems to private cloud. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

Question 646

A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?

  1. Use an incident process to contain service impact and a distinct problem investigation to identify and prevent recurring causes
  2. Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access
  3. Monitor cloud resource capacity and service indicators against agreed SLOs and forecast trends before scale or failure limits are reached
  4. Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A ticketing SaaS restarts a database each Friday but never diagnoses the failing network mount. There, the reason is: Restoring service quickly does not explain why the fault occurred, and a separate cause analysis is needed for durable corrective controls. The current case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

B.

Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. The technical reason is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. The stated condition is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Confirm the result by: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

C.

This action is appropriate in a different case: A cloud university portal hits API rate limits each semester despite normal provider availability. There, the reason is: Provider uptime targets do not ensure an application's end-to-end availability when its own quotas, queues or storage are exhausted. The current case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

This action is appropriate in a different case: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. There, the reason is: Volatile process state disappears on shutdown and uncontrolled collection can overwrite evidence or create privacy violations. The current case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The appropriate response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

Question 647

A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. An engineer recommends: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. 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. An unaltered snapshot cannot be assumed trustworthy if investigators cannot show when and by whom it was captured and handled
  3. Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution
  4. Different audiences need validated operational facts, and premature or missing notices can worsen harm or violate binding commitments

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Capture authorized memory and runtime evidence using a documented, time-bound cloud forensics procedure before restarting affected instances. It applies to: A cloud SOC detects a suspected in-memory credential stealer on a VM scheduled for automatic termination. The actual case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

B.

This principle explains a different technical intervention: Record cloud snapshot source identifiers, signed hashes, access history and transfer events through acquisition and review. It applies to: A public-sector investigator receives cloud snapshots with no timestamp or collection record. The actual case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

C.

Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. That mechanism explains the decision: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. In the reported situation: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Confirmation requires: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

D.

This principle explains a different technical intervention: Use an incident communication matrix that maps severity, contractual notice duties and regulatory decision owners to approved factual updates. It applies to: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. The actual case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The mechanism relevant here is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution.

Question 648

A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?

  1. Simulate a high-severity incident and confirm the right legal, business and supplier contacts receive approved updates within applicable deadlines
  2. Run a tabletop exercise and verify the defined support contact, ticket routing and alternate communication channels actually work
  3. Execute a benign suspicious-login simulation and verify matched identity and API calls appear in one correlated alert
  4. Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Use an incident communication matrix that maps severity, contractual notice duties and regulatory decision owners to approved factual updates. That remedy applies to: A health cloud vendor finds suspicious storage access and wants to notify every customer before validating scope. The present condition is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

B.

This observation would verify a different remedy: Maintain verified cloud provider escalation contacts, dependency owners and customer communication paths for multi-party incidents. That remedy applies to: A logistics company faces a regional provider DNS outage but only its internal application team is informed. The present condition is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

C.

This observation would verify a different remedy: Normalize identity, network, API and workload events into a protected SIEM with correlation rules and tenant-specific context. That remedy applies to: A bank detects unusual API access after a sign-in anomaly but its identity and object logs use incompatible timestamps. The present condition is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. To assess it, check: Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA.

D.

Connect from an untrusted network and confirm the management interface is inaccessible without the approved broker and MFA. This check directly tests: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access. The underlying behavior is: Compromised direct administration exposes broad platform controls while a monitored broker reduces exposed attack surface and improves session attribution. The case is: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access.

Question 649

A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?

  1. Expose all cloud control consoles on unrestricted public IP addresses for operational convenience
  2. Keep each cloud account's raw security logs in short-lived local buffers with no central analysis
  3. Launch unrestricted destructive security tests across a provider region because the organization rents a virtual machine there
  4. Configure any single failed-login alert to delete every account or instance in a cloud organization automatically

Answer & Explanations

Correct answer: A

A.

Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. This shortcut is unsafe for: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The resulting failure can be: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The safer response is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

B.

This proposed shortcut concerns a separate case: A bank detects unusual API access after a sign-in anomaly but its identity and object logs use incompatible timestamps. The risk in this question concerns: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

C.

This proposed shortcut concerns a separate case: A research SaaS team wants to stress-test a managed database endpoint shared with other tenants. The risk in this question concerns: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

This proposed shortcut concerns a separate case: A cloud SOC uses one low-confidence anomaly to revoke every production API credential in an organization. The risk in this question concerns: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Here the unsafe shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Use this response instead: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

Question 650

A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. Suppose the team makes this shortcut instead: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Which outcome is the most likely direct consequence?

  1. An innocuous or manipulated event causes a self-inflicted organization-wide outage
  2. An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account
  3. Publicly reachable customer-managed software remains exploitable despite provider infrastructure maintenance
  4. A departed contractor retains privileged access and investigators cannot attribute destructive changes

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 logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

B.

An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. This is the risk in the stated situation: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The risky shortcut is: Expose all cloud control consoles on unrestricted public IP addresses for operational convenience. Prevent it by: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

C.

This failure concerns another scenario: A financial SaaS runs customer-managed web servers with a published actively exploited package vulnerability. In the stated case: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

D.

This failure concerns another scenario: A managed cloud team allows every vendor engineer to log directly into production VMs with one shared administrator key. In the stated case: A logistics provider wants contractors to troubleshoot cloud servers without handing them permanent direct SSH access. The relevant consequence is: An attacker exploits a stolen password to alter networking, storage or audit configurations across a whole account. The control that prevents it is: Require MFA-protected bastion or privileged access workflow for operational consoles and protect cloud management interfaces from direct public access.

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