Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
An enterprise web service running on a fleet of Compute Engine Linux VMs generates over 40,000 HTTP access log entries per second per instance during peak traffic. The operations team identifies two major issues:
google-fluentd) is reaching its single-core CPU limit and dropping log entries due to buffer overflow.You must design an observability architecture that achieves the following requirements:
Which solution should you implement?
This approach runs multiple google-fluentd instances listening on port 24231, excludes 10% of HTTP 5xx error logs via Cloud Logging exclusion filters, and queries ingested logs with Logs Analytics SQL.
0.0.0.0:24231) triggers Errno::EADDRINUSE fatal binding errors, causing the agent supervisor to fail.Errors were generated at massive volumes during a known stress test and needed rate-limiting to prevent log quota exhaustion.
This approach attempts to resolve agent issues by trimming individual log entry sizes using Fluentd's record_transformer plugin, monitors availability using external uptime checks, and exports all logs to Cloud Storage.
google-fluentd. Adding Ruby-based record_transformer regex manipulation adds CPU overhead per record, worsening CPU saturation and buffer drops.The primary problem was individual oversized log payloads exceeding the 256 KiB Cloud Logging limit resulting in API rejection errors.
This option changes file rotation to copytruncate, forces periodic Logging agent restarts via postrotate, configures log-based metrics downstream inside the log bucket, and exports the full stream to BigQuery.
copytruncate causes the Logging agent to lose file offsets or duplicate entries upon restart, creating severe log corruption.google-fluentd does not increase its single-core processing capability (5,500 logs/sec), leaving the 40,000 logs/sec load unaddressed.The business required full SQL analytics over raw, uncompressed log archives where streaming costs were secondary to complete data fidelity.
This architecture combines the high-throughput Google Cloud Ops Agent with Log-based Metrics and Log Exclusion Filters using deterministic sampling in Cloud Logging.
google-fluentd agent is CPU-bounded and capped at roughly 5,500 entries per second on a single core. Upgrading to the Google Cloud Ops Agent increases throughput capacity to approximately 160,000 log entries per second on Linux, easily handling 40,000 entries per second without buffer overflows.sample(insertId, 0.90) on logs where httpRequest.status < 500 discards 90% of non-error logs before ingestion into the _Default bucket, retaining an exact 10% uniform sample.500 or higher bypass the exclusion filter entirely and are stored in full for debugging and auditing.sample() function hashes fields such as insertId to produce statistically accurate uniform sampling across distributed instances.This design leverages native Cloud Logging pipeline behavior—extracting metric data before exclusion routing—so no monitoring visibility is lost while drastically reducing storage spend and agent compute bottlenecks.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated