PROFESSIONAL-SECURITY-OPERATIONS-ENGINEER · Question #50
You are using a Google-managed image on a Compute Engine instance in Google Cloud to run an application. You need to ingest the application's log output into Google Security Operations (SecOps). The…
The correct answer is A. Use the Ops Agent embedded in the Compute Engine image to pull the logs into Cloud Logging. The most efficient and cost-effective approach is to use the Ops Agent (already embedded in the Compute Engine image) to send logs to Cloud Logging, and then use the direct ingestion mechanism to forward those logs into Google SecOps. This avoids deploying additional agents or…
Question
You are using a Google-managed image on a Compute Engine instance in Google Cloud to run an application. You need to ingest the application's log output into Google Security Operations (SecOps). The log output is standard and has a valid label and parser in Google SecOps. Your solution must minimize the cost and time required to move this data into Google SecOps. What should you do?
Options
- AUse the Ops Agent embedded in the Compute Engine image to pull the logs into Cloud Logging.
- BDeploy a Bindplane agent on the image to collect and send the logs to Google SecOps.
- CCreate a script on the workload that reads the logs and uses the Google SecOps Ingestion API to
- DUse the Ops Agent embedded in the Compute Engine image to pull the logs into a Cloud Storage
How the community answered
(34 responses)- A82% (28)
- B12% (4)
- C3% (1)
- D3% (1)
Explanation
The most efficient and cost-effective approach is to use the Ops Agent (already embedded in the Compute Engine image) to send logs to Cloud Logging, and then use the direct ingestion mechanism to forward those logs into Google SecOps. This avoids deploying additional agents or scripts, leverages Google-managed integrations, and minimizes both cost and time.
Topics
Community Discussion
No community discussion yet for this question.