An organization's typical network and security review consists of analyzing application transit routes, request handling, and firewall rules. They want to enable their developer teams to deploy new…

Question

Options

• AUse Forseti with Firewall filters to catch any unwanted configurations in production.
• BMandate use of infrastructure as code and provide static analysis in the CI/CD pipelines to
• CRoute all VPC traffic through customer-managed routers to detect malicious patterns in
• DAll production applications will run on-premises. Allow developers free rein in GCP as their dev

• A
  14% (4)
• B
  50% (14)
• C
  7% (2)
• D
  29% (8)

Explanation

Mandating Infrastructure as Code (IaC) and adding static analysis tools (such as gcloud-based linters, Terraform validators, or tools like Checkov/tfsec) into CI/CD pipelines shifts security reviews left - catching misconfigurations automatically before they reach production. This eliminates the manual overhead of per-deployment reviews while still enforcing the organization's network and firewall policies at scale. Option A (Forseti) detects issues after deployment to production, which is too late. Option C (customer-managed routers) adds operational overhead and does not replace a security review process. Option D is not a viable enterprise strategy.

No community discussion yet for this question.