Question 640
To monitor host and container runtime behavior inside virtual compute workloads, what is the most direct option?
- Cloud secret rotation
- Cloud security posture management
- Cloud database encryption at rest
- Cloud storage object immutability
- Cloud workload protection
Explanation
Correct Answer
E:CWPP sensors focus on execution and vulnerability exposure rather than only control-plane settings; the requested outcome is precisely to monitor host and container runtime behavior inside virtual compute workloads.
Incorrect Answers
A:Replacing the credential and all consumers closes continued use of the leaked value; that is useful when the task is to limit exposure after a workload password appears in build logs, not the stated requirement to monitor host and container runtime behavior inside virtual compute workloads.
B:CSPM evaluates cloud resource state against secure configuration and compliance rules; a team would select it to detect misconfigured public storage and permissive IAM across subscriptions, which does not provide the particular result to monitor host and container runtime behavior inside virtual compute workloads.
C:Provider or customer-managed keys support storage confidentiality while query access remains separately authorized; its operational purpose is to protect managed database storage against offline media disclosure, not to achieve the specific requirement to monitor host and container runtime behavior inside virtual compute workloads.
D:Retention locks protect copies against destructive changes under approved governance modes; applying it would serve prevent backup objects being deleted before a defined recovery window without directly satisfying the goal to monitor host and container runtime behavior inside virtual compute workloads.
Question 641
To stop a permissive firewall rule from entering production via a template, what should defenders select?
- Cloud workload protection
- Cloud infrastructure as code review
- Cloud database encryption at rest
- Cloud image scanning
Explanation
Correct Answer
B:Static policy checks and pull-request controls catch risky definitions before provisioning; this choice fits the scenario because the team must stop a permissive firewall rule from entering production via a template.
Incorrect Answers
A:CWPP sensors focus on execution and vulnerability exposure rather than only control-plane settings; it could help someone trying to monitor host and container runtime behavior inside virtual compute workloads, but the problem is instead to stop a permissive firewall rule from entering production via a template.
C:Provider or customer-managed keys support storage confidentiality while query access remains separately authorized; a team would select it to protect managed database storage against offline media disclosure, which does not provide the particular result to stop a permissive firewall rule from entering production via a template.
D:Image assessments identify affected operating-system and application components before deployment; its operational purpose is to avoid launching VMs from images with known vulnerable packages, not to achieve the specific requirement to stop a permissive firewall rule from entering production via a template.
Question 642
To protect managed database storage against offline media disclosure, which mechanism best fits?
- Cloud metadata service protection
- Cloud database encryption at rest
- Cloud backup cross-account copy
- Cloud infrastructure as code review
Explanation
Correct Answer
B:Provider or customer-managed keys support storage confidentiality while query access remains separately authorized; this mechanism directly supports the requirement to protect managed database storage against offline media disclosure.
Incorrect Answers
A:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; although relevant to reduce SSRF paths to instance identity tokens, it does not by itself achieve the required task to protect managed database storage against offline media disclosure.
C:Independent account permissions reduce the reach of production administrators into protected backups; that is useful when the task is to retain recoverable data after compromise of a production cloud account, not the stated requirement to protect managed database storage against offline media disclosure.
D:Static policy checks and pull-request controls catch risky definitions before provisioning; a team would select it to stop a permissive firewall rule from entering production via a template, which does not provide the particular result to protect managed database storage against offline media disclosure.
Question 643
To prevent backup objects being deleted before a defined recovery window, which measure best meets the requirement?
- Cloud backup cross-account copy
- Cloud storage object immutability
- Cloud metadata service protection
- Cloud infrastructure as code review
Explanation
Correct Answer
B:Retention locks protect copies against destructive changes under approved governance modes; it supplies the specific control needed to prevent backup objects being deleted before a defined recovery window.
Incorrect Answers
A:Independent account permissions reduce the reach of production administrators into protected backups; the outcome it supports is to retain recoverable data after compromise of a production cloud account, whereas this scenario asks defenders to prevent backup objects being deleted before a defined recovery window.
C:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; it could help someone trying to reduce SSRF paths to instance identity tokens, but the problem is instead to prevent backup objects being deleted before a defined recovery window.
D:Static policy checks and pull-request controls catch risky definitions before provisioning; that is useful when the task is to stop a permissive firewall rule from entering production via a template, not the stated requirement to prevent backup objects being deleted before a defined recovery window.
Question 644
To limit exposure after a workload password appears in build logs, what control should be selected?
- Cloud database encryption at rest
- Cloud image scanning
- Cloud backup cross-account copy
- Cloud secret rotation
Explanation
Correct Answer
D:Replacing the credential and all consumers closes continued use of the leaked value; that is why it addresses the operational task to limit exposure after a workload password appears in build logs.
Incorrect Answers
A:Provider or customer-managed keys support storage confidentiality while query access remains separately authorized; its mechanism supports protect managed database storage against offline media disclosure, while the requested control must be able to limit exposure after a workload password appears in build logs.
B:Image assessments identify affected operating-system and application components before deployment; the outcome it supports is to avoid launching VMs from images with known vulnerable packages, whereas this scenario asks defenders to limit exposure after a workload password appears in build logs.
C:Independent account permissions reduce the reach of production administrators into protected backups; although relevant to retain recoverable data after compromise of a production cloud account, it does not by itself achieve the required task to limit exposure after a workload password appears in build logs.
Question 645
To retain recoverable data after compromise of a production cloud account, which security control is most appropriate?
- Cloud container registry access
- Cloud secret rotation
- Cloud storage object immutability
- Cloud image scanning
- Cloud backup cross-account copy
Explanation
Correct Answer
E:Independent account permissions reduce the reach of production administrators into protected backups; its relevant protective or investigative effect is to retain recoverable data after compromise of a production cloud account.
Incorrect Answers
A:Repository policies distinguish artifact read and write rights from workload runtime permissions; the technique works for situations involving stop outside teams pulling proprietary deployment images, rather than this need to retain recoverable data after compromise of a production cloud account.
B:Replacing the credential and all consumers closes continued use of the leaked value; its mechanism supports limit exposure after a workload password appears in build logs, while the requested control must be able to retain recoverable data after compromise of a production cloud account.
C:Retention locks protect copies against destructive changes under approved governance modes; the outcome it supports is to prevent backup objects being deleted before a defined recovery window, whereas this scenario asks defenders to retain recoverable data after compromise of a production cloud account.
D:Image assessments identify affected operating-system and application components before deployment; although relevant to avoid launching VMs from images with known vulnerable packages, it does not by itself achieve the required task to retain recoverable data after compromise of a production cloud account.
Question 646
To avoid launching VMs from images with known vulnerable packages, what would a cloud security architect implement or use?
- Cloud backup cross-account copy
- Cloud secret rotation
- Cloud image scanning
- Cloud metadata service protection
- Cloud storage object immutability
- Cloud container registry access
Explanation
Correct Answer
C:Image assessments identify affected operating-system and application components before deployment; the requested outcome is precisely to avoid launching VMs from images with known vulnerable packages.
Incorrect Answers
A:Independent account permissions reduce the reach of production administrators into protected backups; it addresses the different need to retain recoverable data after compromise of a production cloud account, leaving the requested ability to avoid launching VMs from images with known vulnerable packages unresolved.
B:Replacing the credential and all consumers closes continued use of the leaked value; the technique works for situations involving limit exposure after a workload password appears in build logs, rather than this need to avoid launching VMs from images with known vulnerable packages.
D:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; the outcome it supports is to reduce SSRF paths to instance identity tokens, whereas this scenario asks defenders to avoid launching VMs from images with known vulnerable packages.
E:Retention locks protect copies against destructive changes under approved governance modes; although relevant to prevent backup objects being deleted before a defined recovery window, it does not by itself achieve the required task to avoid launching VMs from images with known vulnerable packages.
F:Repository policies distinguish artifact read and write rights from workload runtime permissions; it could help someone trying to stop outside teams pulling proprietary deployment images, but the problem is instead to avoid launching VMs from images with known vulnerable packages.
Question 647
To reduce SSRF paths to instance identity tokens, which practice addresses that objective?
- Cloud secret rotation
- Cloud storage object immutability
- Cloud backup cross-account copy
- Cloud metadata service protection
Explanation
Correct Answer
D:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; this choice fits the scenario because the team must reduce SSRF paths to instance identity tokens.
Incorrect Answers
A:Replacing the credential and all consumers closes continued use of the leaked value; applying it would serve limit exposure after a workload password appears in build logs without directly satisfying the goal to reduce SSRF paths to instance identity tokens.
B:Retention locks protect copies against destructive changes under approved governance modes; it addresses the different need to prevent backup objects being deleted before a defined recovery window, leaving the requested ability to reduce SSRF paths to instance identity tokens unresolved.
C:Independent account permissions reduce the reach of production administrators into protected backups; the technique works for situations involving retain recoverable data after compromise of a production cloud account, rather than this need to reduce SSRF paths to instance identity tokens.
Question 648
To stop outside teams pulling proprietary deployment images, which tool, policy, or technique is appropriate?
- Cloud container registry access
- Cloud image scanning
- Cloud metadata service protection
- Cloud backup cross-account copy
Explanation
Correct Answer
A:Repository policies distinguish artifact read and write rights from workload runtime permissions; this mechanism directly supports the requirement to stop outside teams pulling proprietary deployment images.
Incorrect Answers
B:Image assessments identify affected operating-system and application components before deployment; applying it would serve avoid launching VMs from images with known vulnerable packages without directly satisfying the goal to stop outside teams pulling proprietary deployment images.
C:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; it addresses the different need to reduce SSRF paths to instance identity tokens, leaving the requested ability to stop outside teams pulling proprietary deployment images unresolved.
D:Independent account permissions reduce the reach of production administrators into protected backups; the technique works for situations involving retain recoverable data after compromise of a production cloud account, rather than this need to stop outside teams pulling proprietary deployment images.
Question 649
To reduce SSRF paths to instance identity tokens, to stop outside teams pulling proprietary deployment images, and to associate exposed assets with accountable project teams and data owners, which THREE measures should the team select? Choose THREE.
- Cloud container registry access
- Cloud image scanning
- Cloud secret rotation
- Cloud metadata service protection
- Cloud resource tagging
- Cloud backup cross-account copy
Explanation
Correct Answers
A:Repository policies distinguish artifact read and write rights from workload runtime permissions; its contribution to the combined design is specifically to stop outside teams pulling proprietary deployment images.
D:Restricting metadata access and using hardened token mechanisms limit credential retrieval through web flaws; its contribution to the combined design is specifically to reduce SSRF paths to instance identity tokens.
E:Mandatory metadata improves cleanup, cost allocation and remediation routing for discoveries; its contribution to the combined design is specifically to associate exposed assets with accountable project teams and data owners.
Incorrect Answers
B:Image assessments identify affected operating-system and application components before deployment; its operational purpose is to avoid launching VMs from images with known vulnerable packages, not to achieve the specific requirement to reduce SSRF paths to instance identity tokens, to stop outside teams pulling proprietary deployment images, and to associate exposed assets with accountable project teams and data owners.
C:Replacing the credential and all consumers closes continued use of the leaked value; applying it would serve limit exposure after a workload password appears in build logs without directly satisfying the goal to reduce SSRF paths to instance identity tokens, to stop outside teams pulling proprietary deployment images, and to associate exposed assets with accountable project teams and data owners.
F:Independent account permissions reduce the reach of production administrators into protected backups; its mechanism supports retain recoverable data after compromise of a production cloud account, while the requested control must be able to reduce SSRF paths to instance identity tokens, to stop outside teams pulling proprietary deployment images, and to associate exposed assets with accountable project teams and data owners.
Question 650
To identify production resources changed outside approved infrastructure templates, what safeguard would be most applicable?
- Cloud configuration drift detection
- Cloud region outage planning
- Cloud provider assurance review
- Cloud penetration-testing authorization
- Cloud log archive isolation
Explanation
Correct Answer
A:State comparison exposes deviations that may introduce access or availability weaknesses; that is why it addresses the operational task to identify production resources changed outside approved infrastructure templates.
Incorrect Answers
B:Multi-region architectures require independent recovery design and data-consistency decisions; a team would select it to preserve service availability when one deployment region becomes unavailable, which does not provide the particular result to identify production resources changed outside approved infrastructure templates.
C:Independent attestations inform inherited controls but must be matched to the actual service scope; its operational purpose is to evaluate service compliance reports before entrusting regulated data, not to achieve the specific requirement to identify production resources changed outside approved infrastructure templates.
D:Provider policies and tenant change approval define permissible testing boundaries; applying it would serve avoid violating provider rules during an approved security assessment without directly satisfying the goal to identify production resources changed outside approved infrastructure templates.
E:Separate immutable retention and narrowly scoped writer roles defend evidence after compromise; it addresses the different need to keep attackers with workload access from deleting audit history, leaving the requested ability to identify production resources changed outside approved infrastructure templates unresolved.