ISC CCSP Dumps
ISC CCSP Practice Test 35
Question 340
A laboratory places orchestration credentials inside a guest that also has access to host control sockets. Suppose the team makes this shortcut instead: Expose the hypervisor management API on an unrestricted tenant-facing subnet to simplify VM troubleshooting. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: D
This failure concerns another scenario: A clinical archive encrypts sensitive cloud volumes but lets its general help desk rotate and export all wrapping keys. In the stated case: A laboratory places orchestration credentials inside a guest that also has access to host control sockets. The relevant consequence is: A compromised guest gains an opportunity to manipulate host or neighboring tenant resources. The control that prevents it is: Segment cloud hypervisor management endpoints and require privileged access through a monitored administrative plane.
This failure concerns another scenario: A cloud commerce site promises fifteen-minute data loss but captures customer orders only every twelve hours. In the stated case: A laboratory places orchestration credentials inside a guest that also has access to host control sockets. The relevant consequence is: A compromised guest gains an opportunity to manipulate host or neighboring tenant resources. The control that prevents it is: Segment cloud hypervisor management endpoints and require privileged access through a monitored administrative plane.
This failure concerns another scenario: A government portal has redundant compute regions but all recovery keys are held in the primary cloud region. In the stated case: A laboratory places orchestration credentials inside a guest that also has access to host control sockets. The relevant consequence is: A compromised guest gains an opportunity to manipulate host or neighboring tenant resources. The control that prevents it is: Segment cloud hypervisor management endpoints and require privileged access through a monitored administrative plane.
A compromised guest gains an opportunity to manipulate host or neighboring tenant resources. This is the risk in the stated situation: A laboratory places orchestration credentials inside a guest that also has access to host control sockets. The risky shortcut is: Expose the hypervisor management API on an unrestricted tenant-facing subnet to simplify VM troubleshooting. Prevent it by: Segment cloud hypervisor management endpoints and require privileged access through a monitored administrative plane.
Question 341
A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: A
Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. The technical reason is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. The stated condition is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Confirm the result by: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This action is appropriate in a different case: A manufacturer gives its mobile app developers production-wide cloud network permissions for routine deployments. There, the reason is: Control-plane permissions can modify networks, storage and identity across many workloads, making a broad account more dangerous than an individual VM account. The current case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This action is appropriate in a different case: A healthcare private cloud is built on a single unfiltered VLAN shared by user applications and hypervisor consoles. There, the reason is: Logical separation reduces lateral movement and helps prevent ordinary application traffic from reaching privileged infrastructure functions. The current case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This action is appropriate in a different case: An insurer selects a coastal facility for its only backup copy without evaluating local flood exposure. There, the reason is: Locational and facility risks include flood, jurisdiction, unauthorized access and shared physical dependencies beyond virtual access controls. The current case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Question 342
A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. An engineer recommends: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: B
This principle explains a different technical intervention: Select cloud sites that satisfy documented hazard, residency, physical security and supplier continuity requirements. It applies to: An insurer selects a coastal facility for its only backup copy without evaluating local flood exposure. The actual case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. That mechanism explains the decision: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. In the reported situation: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Confirmation requires: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This principle explains a different technical intervention: Model relevant co-tenant resource sharing threats and apply supported isolation, dedicated capacity or confidential computing where the workload justifies it. It applies to: A government research workload processes highly sensitive models on shared commodity cloud hosts. The actual case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
This principle explains a different technical intervention: Quantify the business impact of losing a critical cloud provider region or identity service and document acceptable risk treatment. It applies to: A payment platform depends on one cloud identity service in a single region despite cross-zone application replicas. The actual case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
Question 343
A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: C
This observation would verify a different remedy: Quantify the business impact of losing a critical cloud provider region or identity service and document acceptable risk treatment. That remedy applies to: A payment platform depends on one cloud identity service in a single region despite cross-zone application replicas. The present condition is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This observation would verify a different remedy: Record threat likelihood, business impact, residual exposure and accountable approval before selecting mitigate, transfer, avoid or accept. That remedy applies to: A small SaaS business considers accepting the cost of redundant storage after reviewing expected loss. The present condition is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval. This check directly tests: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. The underlying behavior is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. The case is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges.
This observation would verify a different remedy: Define least-privilege workload ingress and east-west network controls from verified service communication requirements. That remedy applies to: A hospital web application should reach one patient database but is allowed to connect to every research project subnet. The present condition is: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
Question 344
A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: D
This proposed shortcut concerns a separate case: A hospital web application should reach one patient database but is allowed to connect to every research project subnet. The risk in this question concerns: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This proposed shortcut concerns a separate case: A cloud operations team has twenty permanent administrators but typically needs write access for one planned maintenance hour. The risk in this question concerns: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This proposed shortcut concerns a separate case: A clinical archive encrypts sensitive cloud volumes but lets its general help desk rotate and export all wrapping keys. The risk in this question concerns: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. This shortcut is unsafe for: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The resulting failure can be: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The safer response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Question 345
A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. Suppose the team makes this shortcut instead: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: A
An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. This is the risk in the stated situation: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The risky shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Prevent it by: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This failure concerns another scenario: A clinical archive encrypts sensitive cloud volumes but lets its general help desk rotate and export all wrapping keys. In the stated case: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This failure concerns another scenario: A cloud commerce site promises fifteen-minute data loss but captures customer orders only every twelve hours. In the stated case: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This failure concerns another scenario: A government portal has redundant compute regions but all recovery keys are held in the primary cloud region. In the stated case: A photo-processing API fetches user-supplied URLs from a VM with broad object-store privileges. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Question 346
A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Which cloud security control or governance decision most directly addresses the described issue while keeping the change scoped?
Answer & Explanations
Correct answer: B
This action is appropriate in a different case: An insurer selects a coastal facility for its only backup copy without evaluating local flood exposure. There, the reason is: Locational and facility risks include flood, jurisdiction, unauthorized access and shared physical dependencies beyond virtual access controls. The current case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. The technical reason is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. The stated condition is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Confirm the result by: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This action is appropriate in a different case: A government research workload processes highly sensitive models on shared commodity cloud hosts. There, the reason is: Virtualization isolation can be strong yet some shared hardware features create residual co-residency or side-channel threats. The current case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This action is appropriate in a different case: A payment platform depends on one cloud identity service in a single region despite cross-zone application replicas. There, the reason is: Multiple application instances do not remove provider concentration when all depend on the same control-plane or region. The current case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The appropriate response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Question 347
A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. An engineer recommends: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. Which technical explanation most directly justifies this recommendation?
Answer & Explanations
Correct answer: C
This principle explains a different technical intervention: Quantify the business impact of losing a critical cloud provider region or identity service and document acceptable risk treatment. It applies to: A payment platform depends on one cloud identity service in a single region despite cross-zone application replicas. The actual case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
This principle explains a different technical intervention: Record threat likelihood, business impact, residual exposure and accountable approval before selecting mitigate, transfer, avoid or accept. It applies to: A small SaaS business considers accepting the cost of redundant storage after reviewing expected loss. The actual case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. That mechanism explains the decision: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. In the reported situation: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Confirmation requires: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This principle explains a different technical intervention: Define least-privilege workload ingress and east-west network controls from verified service communication requirements. It applies to: A hospital web application should reach one patient database but is allowed to connect to every research project subnet. The actual case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The mechanism relevant here is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens.
Question 348
A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. After applying the relevant fix, which observable evidence would most convincingly establish that the underlying issue has been resolved?
Answer & Explanations
Correct answer: D
This observation would verify a different remedy: Define least-privilege workload ingress and east-west network controls from verified service communication requirements. That remedy applies to: A hospital web application should reach one patient database but is allowed to connect to every research project subnet. The present condition is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This observation would verify a different remedy: Require time-bound approved administrator elevation through a managed privileged-access gateway instead of permanent standing broad rights. That remedy applies to: A cloud operations team has twenty permanent administrators but typically needs write access for one planned maintenance hour. The present condition is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
This observation would verify a different remedy: Apply storage encryption using approved managed keys with separate key-admin and data-admin roles and reliable audit trails. That remedy applies to: A clinical archive encrypts sensitive cloud volumes but lets its general help desk rotate and export all wrapping keys. The present condition is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. To assess it, check: Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval.
Run authorized SSRF-style tests in staging and confirm metadata access controls prevent unrelated credential retrieval. This check directly tests: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials. The underlying behavior is: Cloud metadata endpoints can issue temporary workload credentials, and unrestricted server-side fetches may expose those tokens. The case is: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible.
Question 349
A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Which apparently convenient shortcut would most directly undermine safe resolution of this specific situation?
Answer & Explanations
Correct answer: A
Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. This shortcut is unsafe for: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The resulting failure can be: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The safer response is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This proposed shortcut concerns a separate case: A clinical archive encrypts sensitive cloud volumes but lets its general help desk rotate and export all wrapping keys. The risk in this question concerns: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This proposed shortcut concerns a separate case: A cloud commerce site promises fifteen-minute data loss but captures customer orders only every twelve hours. The risk in this question concerns: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This proposed shortcut concerns a separate case: A government portal has redundant compute regions but all recovery keys are held in the primary cloud region. The risk in this question concerns: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Here the unsafe shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Use this response instead: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Question 350
A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. Suppose the team makes this shortcut instead: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Which outcome is the most likely direct consequence?
Answer & Explanations
Correct answer: B
This failure concerns another scenario: A government portal has redundant compute regions but all recovery keys are held in the primary cloud region. In the stated case: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. This is the risk in the stated situation: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The risky shortcut is: Allow arbitrary user-controlled URLs to be fetched by a privileged application with unrestricted access to instance metadata. Prevent it by: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This failure concerns another scenario: A credit union stores weekly backup objects but has never restored the payment system from them. In the stated case: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
This failure concerns another scenario: A public records service has four cloud VMs but all run in one availability zone with a shared power dependency. In the stated case: A cloud developer moves a vulnerable URL preview service to compute nodes where metadata credentials are accessible. The relevant consequence is: An attacker obtains temporary cloud credentials and reads resources outside the web application's intended authority. The control that prevents it is: Use scoped instance identity tokens and metadata-service hardening to prevent untrusted processes from obtaining other workloads' credentials.
Certified Cloud Security Professional (CCSP) (CCSP) Practice Tests
- ISC CCSP Practice Test 33 - 10 Questions (Last Reviewed 18-Oct-2026)
- ISC CCSP Practice Test 34 - 10 Questions (Last Reviewed 17-Oct-2026)
- ISC CCSP Practice Test 35 - 10 Questions (Last Reviewed 16-Oct-2026)
- ISC CCSP Practice Test 36 - 10 Questions (Last Reviewed 15-Oct-2026)
- ISC CCSP Practice Test 37 - 10 Questions (Last Reviewed 14-Oct-2026)