CompTIA Cloud+ guideStudy & preparation

CompTIA Cloud+ Observability: Choose Logs, Metrics or Traces

Published 6 min read4 official sources

Short answer

Choose metrics for measured behavior and trends, logs for recorded events, and traces for the path and timing of an individual request. OpenTelemetry distinguishes these three signals, while CompTIA Cloud+ CV0-004 objective 3.1 covers logging, tracing and monitoring. Combine signals when the first observation leaves a question unanswered; a matching timestamp or a slow span alone does not establish the cause of an incident.

What question does each telemetry signal answer?

Choose metrics for measured behavior, logs for event details, and traces for the path and timing of one request. OpenTelemetry describes metrics as runtime measurements, logs as event records, and traces as a way to follow a request through an application and its services.

CompTIA includes logging, tracing and monitoring in Cloud+ CV0-004 objective 3.1. That exam scope comes from the objectives checked November 11, 2026; OpenTelemetry's metrics and logs documentation was checked November 14, and the trace evidence was checked November 11. These sources support the distinctions below, not a prediction of a particular exam question.

The question you need to answerStart withWhat to look forWhat remains open
Is the queue growing over time?MetricsComparable queue measurements over a stated intervalWhy the queue is growing
What error did a worker record?LogsEvent, time, service and relevant contextWhether that event explains the wider incident
Where did this request spend time?TracesThe recorded request path and timingsWhy a step took that long

Write the question before choosing the signal. If you need the broader exam map, use the guide to what is on the CompTIA Cloud+ exam.

When does an aggregate metric hide an individual problem?

Metrics summarize measured behavior. OpenTelemetry distinguishes counters that accumulate, gauges that capture current values, and histograms that describe distributions such as request latency. Those are different ways to describe observations, so inspect what a chart actually measures before treating it as an answer. Metric types like these are recall facts, which recall flashcards planned for full CompTIA Cloud+ prep can help with.

Standalone mini-case 1 — a trend question. A fictional batch service reports queue counts of 12, 24 and 41 at three successive observations. The question asks whether the queue is growing. Choose the queue metric: the observed counts increase across that interval. You still do not know why, and the values alone do not identify a particular delayed request.

A normal CPU chart answers a question about the measured CPU behavior. It does not establish that every request is healthy. If the next question asks where one request waited, move to its recorded trace instead of adding more CPU observations.

All case names, identifiers, counts and times in this article are fictional teaching inputs, not production benchmarks or CompTIA exam content. For each metric, write its scope and time interval next to your conclusion.

What makes a log useful for correlation?

A log records an event, with a timestamp and optional metadata. OpenTelemetry explains that consistent structured fields help parsing and correlation. JSON formatting alone does not guarantee that different records use the same field names and meanings.

Useful context might identify the service, the event and an associated request. OpenTelemetry's log model includes TraceId and SpanId fields that can connect a record to request context. Their presence and usable values must be checked; correlation is not automatic in every system.

Standalone mini-case 2 — an event question. A fictional thumbnail worker records an unsupported_format event. The question asks which service reported the event and what it reported. Choose the log containing those fields. The warranted answer is that the named worker recorded that event. The record does not establish how many other requests were affected or prove that this event caused a separate queue alert.

Before connecting records, check their service, time window and available request context. If those details are absent, state the gap rather than declaring a match.

How do you follow one request across services?

A trace provides a recorded path through an application and its services, with context for where a request spends time. It is useful when the question concerns that journey rather than a population of requests or a single event message.

Standalone mini-case 3 — a path question. A fictional report request has recorded timings for receiving the request, retrieving its input and rendering the result. The input-retrieval step takes 800 milliseconds; rendering takes 35 milliseconds. Choose the trace when asked which recorded step took longer. The observation supports input retrieval as the longer of these two steps for this request. It does not explain why retrieval was slow or establish the typical timing of all report requests.

Do not assume a trace exists or captures every step. Name the portion of the path actually shown, then identify the next evidence needed. A capacity change is a separate decision; the Cloud+ scaling guide addresses that choice after the relevant constraints are understood.

How do the three signals work together in a case?

Consider Pixel Workshop, a fictional image-processing service. Its investigation uses three records from the same stated incident window. The log and trace are explicitly linked by a matching fictional TraceId in the exercise; their association is given evidence, not a match inferred from timing alone.

StageObserved clueWarranted conclusionUnresolved question and next evidence
Queue metricQueue counts are 20, 45 and 80 at 09:00, 09:01 and 09:02The measured queue grows across those observationsWhat is happening to processing? Inspect relevant event records and request paths
Structured logAt 09:02, service image-worker records source_read_timeout with the supplied TraceIdThat worker recorded this event for the linked requestWhere did that request spend time? Inspect its available trace
Request traceThe linked request records 900 milliseconds waiting for source retrieval and 40 milliseconds in image transformationSource retrieval is the longer recorded step in this exampleWhy did retrieval take that time, and is the pattern widespread? Seek evidence about retrieval and other requests

The combined evidence narrows the investigation. It still does not prove that every queued image encountered the same delay, or that a particular infrastructure fault caused it. Keep the queue trend, the recorded event and the request's timing as three separate observations in your answer. To practice that discipline on more items, see the Operations-domain questions planned for CompTIA Cloud+ prep.

A strong response would say: “The queue grew during the window. One linked worker event and trace point to source retrieval as a place to investigate for that request. I need broader retrieval evidence before applying that explanation to the whole queue.”

Avoid jumping from “there is a delay” to “increase capacity.” If the scenario instead supplies an API-control constraint, use the separate guide to API throttling and service quotas to assess that evidence.

What evidence should your next answer cite?

Use this blank table with a new scenario before looking at its explanation. Keep the observed clue separate from your interpretation.

Question to answerSignal and exact clueSupported conclusionWhat remains unknownNext evidence to request
__________________________________________________
__________________________________________________
__________________________________________________

Then check three things: Did you choose a signal that answers the question? Did you cite the actual observation? Did your conclusion stay within its scope? The explanation planned for every question in full CompTIA Cloud+ prep gives you something to check those points against.

Try that process with the 20 free Cloud+ practice questions, recording the clue that justified each choice. Use the free Cloud+ study plan to organize further review, and bring this evidence table to the next observability exercise. The next useful step is to explain one answer with its evidence and one unresolved question, not simply memorize three definitions.

Trust the source

Official sources

Exam policies can change. Use these primary sources for the most current details.