PCDOE Implementing service monitoring strategies Practice Question

Exhibit

Refer to the exhibit.
```json
{
  "insertId": "abc123",
  "severity": "ERROR",
  "jsonPayload": {
    "message": "Connection timeout",
    "service": "auth-service"
  },
  "resource": {
    "type": "cloud_function",
    "labels": {
      "function_name": "process_login"
    }
  }
}
```

Based on the exhibit, which Cloud Logging query filter will return all logs of this type?

⚠ Common exam trap

Google Cloud often tests the distinction between exact match (`=`) and text search (`:`) operators in Cloud Logging, and candidates mistakenly apply SQL-like range operators (`>=`) or confuse the severity field with a JSON payload field.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

severity=ERROR

Cloud Logging uses the `severity=ERROR` syntax to filter logs by exact severity level. The `=` operator performs an exact match on the severity field, which is a standard LogEntry field with predefined values (DEFAULT, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY). This filter returns all logs where the severity is exactly ERROR, matching the requirement.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
severity>=ERROR
Why it's wrong here
The >= operator is not supported for severity field; severity is a string.
✗
severity:"ERROR"
Why it's wrong here
Colon is used for has operator, not equality.
✓
severity=ERROR
Why this is correct
This is the correct syntax to match logs with severity exactly 'ERROR'.
✗
jsonPayload.severity:ERROR
Why it's wrong here
severity is a top-level field, not inside jsonPayload.

Go deeper

PCDOE Implementing service monitoring strategies Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question