Question 970
In this retired AZ-500 educational case, A multicloud organization uses Defender for Cloud for Azure and AWS but ignores its separate GCP production project fleet. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: A partial connector footprint leaves unmanaged cloud exposure outside reported posture. That is why the action is: Onboard eligible GCP scope and reconcile all environment inventories. The directly relevant confirmation is: The expected GCP project resources become visible with assessed findings.
Incorrect Answers
This alternative is valid when automation rule conditions and playbook resource authorization must both allow invocation. The facts here establish a different controlling reason: A partial connector footprint leaves unmanaged cloud exposure outside reported posture.
“Connector deployment alone does not ensure that telemetry is arriving in the workspace” reflects the mechanism: Connector deployment alone does not ensure that telemetry is arriving in the workspace. The actual reported symptoms are better explained by: A partial connector footprint leaves unmanaged cloud exposure outside reported posture.
The offered principle describes: Policy evaluation and policy-driven resource remediation can require different authorization capabilities. The situation in this question instead depends on: A partial connector footprint leaves unmanaged cloud exposure outside reported posture. These are different technical conditions.