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.
Your team is building an automated incident triage service hosted outside Google Cloud that consumes alert notifications from Cloud Monitoring. The security team establishes the following technical requirements for the integration:
How should you configure the custom webhook notification channel in Cloud Monitoring and the receiving service?
This approach places the shared authentication token in the query string parameter of an unencrypted HTTP URL (for example, http://monitoring-receiver.example.com/alerts?auth_token=SECRET_VALUE).
The external receiver was located inside an isolated, private test network with strictly no external connectivity and no requirement for payload or credential encryption.
Cloud Monitoring token authentication explicitly requires the use of SSL/TLS (HTTPS) to prevent unauthorized parties from learning the token during network transit.
HMAC signature verification involves generating a cryptographic hash of the JSON payload body using a secret key and attaching the signature to an HTTP header (such as X-Hub-Signature-256), allowing the receiving endpoint to verify payload integrity and origin.
The scenario allowed deploying a serverless integration layer (e.g., Cloud Functions or Eventarc) to transform, sign, and deliver webhook payloads to third-party endpoints requiring cryptographic signatures.
To secure Cloud Monitoring webhooks natively without custom compute layers, administrators should utilize HTTPS endpoints paired with query-based token authentication or RFC-compliant Basic Authentication.
Token-based authentication for Cloud Monitoring webhooks is a mechanism where a unique shared secret token is passed directly within the endpoint URL's query string (for example, https://monitoring-receiver.example.com/alerts?auth_token=SECRET_VALUE). When Cloud Monitoring triggers an alert notification, it issues an HTTP POST request to this target URL, allowing the external receiving service to extract and validate the token parameter before processing the incident payload.
auth_token), comparing the value against a securely stored secret key. If the token is missing or incorrect, the server rejects the request with an HTTP 401 Unauthorized or 403 Forbidden status code.This design directly fulfills all security and architectural constraints using native Cloud Monitoring webhook functionality. Combining query-based token authentication with TLS provides confidentiality and origin verification with minimal operational overhead.
HTTP Basic Authentication follows RFC specifications where an initial unauthenticated request to a protected endpoint triggers an HTTP 401 Unauthorized response containing a WWW-Authenticate header. The client (Cloud Monitoring) then retries the request with the Authorization header containing the Base64-encoded username and password.
401 status code and a valid WWW-Authenticate: Basic ... header. If the external server does not issue this 401 challenge, standard HTTP basic authentication negotiation cannot complete successfully.Authorization HTTP header rather than query parameters.The receiving server fully implemented standard HTTP Basic Authentication by responding with a 401 status code and WWW-Authenticate header upon receiving an unauthenticated request.
When using Basic Authentication with Cloud Monitoring, the target server must adhere to RFC 2617 and prompt the client with a 401 response before credentials can be validated.
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