QuestionQ76

VerifiedImplementing observability practices and troubleshooting issues

You are running a real-time gaming application on Compute Engine that has separate production and testing environments. Each environment has its own Virtual Private Cloud (VPC) network, and within each environment's VPC, the application frontend and backend servers reside on different subnets.

You suspect that a malicious process is intermittently communicating from your production frontend servers. You want to ensure that network traffic is captured for analysis.

What should you do?

Explanation

VPC Flow Logs should be enabled only on the production VPC's frontend and backend subnets, since that is where the suspected malicious activity is occurring; enabling flow logs on the testing environment is unnecessary and wasteful. The sampling rate must be set to 1.0 so that all flows are captured (a rate of 0.5 would only log a random half of the flows, risking missing the intermittent malicious communication). This aligns with Google Cloud's guidance that VPC Flow Logs sampling rate controls what fraction of flows are logged, and a value of 1.0 captures 100% of flows for full analysis fidelity.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!