Question 190
During a cloud security review, the operations team observes: A Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation. What should the engineer implement first to address the weakness?
Explanation
Correct Answer
The cause is: Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The appropriate change is: Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment. Verify it with this outcome: The updated template passes the security assessment and the deployed database is not unintentionally public.
Incorrect Answers
This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The reported incident instead involves Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls.
This action concerns defender for cloud workflow automation trigger scope, where A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The corrective response here is “Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment”; this alternative does not provide that response.
This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The stem reports a Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation; this control addresses a different failure condition.