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 e-commerce platform hosted on Google Cloud requires an automated synthetic monitoring strategy to proactively detect performance regressions and functional failures before end users are impacted. The DevOps engineering team must satisfy the following distinct monitoring requirements:
Which combination of synthetic monitoring architectures should the DevOps team implement?
This option attempts to use basic Cloud Monitoring Uptime Checks to execute multi-step browser user journeys and store private service account keys.
All application components were static, public HTTP endpoints that only required a simple status code 200 OK or single string-match verification from global locations.
Cloud Monitoring separates synthetic observability into two tiers: basic Uptime Checks for simple ping/response validation and Synthetic Monitors (Cloud Functions with Puppeteer/Mocha) for programmatic, multi-step user workflows.
This option relies on log-based metrics in Cloud Logging and scheduled analytical queries in BigQuery to detect errors and latency trends from incoming production server traffic.
The goal was to conduct offline historical trend analysis or calculate long-term business Service Level Indicators (SLIs) over months of historical telemetry.
Synthetic monitoring is designed specifically to probe endpoints proactively on a continuous schedule regardless of actual user traffic volume.
This architecture combines native Cloud Monitoring Uptime Checks with Custom Synthetic Monitors implemented as Cloud Functions (2nd gen) leveraging the open-source Synthetic SDK (built on Mocha and Puppeteer) and IAM service account authentication.
This design aligns precisely with Google Cloud observability best practices by pairing lightweight managed probes for simple ping/status checks with programmable serverless execution environments for complex synthetic transactions.
This approach builds a custom, self-hosted testing infrastructure using Compute Engine virtual machines to host Selenium Grid nodes and uses static service account key files downloaded to disk.
The testing architecture required legacy browser engines (such as Internet Explorer) that are unsupported in modern containerized and serverless environments.
Google Cloud recommends replacing persistent credentials with short-lived credentials and using native serverless runtimes (such as Cloud Functions) with attached service accounts.
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