Question 440
The plan uses VM Manager automated security patches for the requirement: The security team wants to verify that selected VMs received a scheduled package update without opening SSH sessions to each instance. What makes this control work?
Explanation
Correct Answer
The operative mechanism for VM Manager automated security patches: Configure VM Manager OS patch deployment with a defined scope, schedule and appropriate maintenance constraints. For this scenario (the security team wants to verify that selected vms received a scheduled package update without opening ssh sessions to each instance), verify that the update job records both failures and successful patch completions for the maintenance window.
Incorrect Answers
This describes how Custom organization policy constraints works instead: Define an appropriate supported custom organization policy constraint and bind its policy at the intended hierarchy level. It is useful when a developer attempts a disallowed resource attribute value that should be blocked at creation rather than detected later, but it does not explain the selected VM Manager automated security patches for the current requirement (the security team wants to verify that selected vms received a scheduled package update without opening ssh sessions to each instance).
This describes how Artifact Registry vulnerability scanning works instead: Enable supported artifact vulnerability scanning and consume the scan occurrence or severity findings in the release review. It is useful when a security team needs a recurring view of vulnerability findings in images stored in a controlled artifact registry repository, but it does not explain the selected VM Manager automated security patches for the current requirement (the security team wants to verify that selected vms received a scheduled package update without opening ssh sessions to each instance).
This describes how Container scanning exception expiry works instead: Maintain scoped documented exceptions and enforce expiration or review in the vulnerability release gate. It is useful when the release team needs an accountable owner and an expiration date for an approved vulnerability exception, but it does not explain the selected VM Manager automated security patches for the current requirement (the security team wants to verify that selected vms received a scheduled package update without opening ssh sessions to each instance).






Professional Cloud Security Engineer Practice Tests