Question 1070
In this retired AZ-500 educational case, A Terraform file has insecure public network settings and a team waits until deployment to run Defender checks. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Preventive code scanning can detect cloud misconfiguration before resources are provisioned. That is why the action is: Integrate supported infrastructure-as-code security assessment early in the DevOps process. The directly relevant confirmation is: A pull-request test surfaces the insecure setting and a revised template passes evaluation.
Incorrect Answers
The offered principle describes: Posture recommendation status can lag behind recently changed resources. The situation in this question instead depends on: Preventive code scanning can detect cloud misconfiguration before resources are provisioned. These are different technical conditions.
This alternative is valid when not every configuration recommendation can be applied instantly, but exceptions need governance. The facts here establish a different controlling reason: Preventive code scanning can detect cloud misconfiguration before resources are provisioned.
“Security operations authorization is distinct from broad Azure resource inspection permissions” reflects the mechanism: Security operations authorization is distinct from broad Azure resource inspection permissions. The actual reported symptoms are better explained by: Preventive code scanning can detect cloud misconfiguration before resources are provisioned.