Observability and Monitoring Quiz

What is the key difference between Monitoring and Observability?

• Monitoring is only for logs; observability includes dashboards

• Monitoring is proactive; observability is reactive

• Monitoring shows predefined metrics; observability helps explore unknowns

• Monitoring includes tracing, observability does not

Which of the following best defines a Trace?

• Number of requests over time

• Structured log of an error

• A timeline of events tied to a single request across services

• A dashboard metric showing CPU utilization

What does SLI stand for in SRE terminology?

• Service Latency Indicator

• Service-Level Insight

• Service-Level Indicator

• System-Level Interface

True or False: An SLO is the agreement between the user and the provider.

• True

• False

Which one of these describes a good alert?

• “CPU usage is over 80% for 5 minutes.”

• “99% of requests exceed 2s for 5 mins — potential SLO breach.”

• “Disk usage exceeded 90%.”

• “A pod restarted 3 times.”

What is the primary value of fast feedback loops in DevOps?

• More frequent meetings

• Better UI design

• Shorter time between failure and learning

• High-volume logging

What makes an alert “actionable”?

• It is sent via SMS

• It includes detailed charts

• It requires a human to take immediate action

• It happens frequently to build awareness

What is the key reason why alerts should be tied to SLOs?

• To reduce CPU usage

• To wake up engineers quickly

• To minimize irrelevant alerts and focus on user experience

• To monitor error logs more efficiently

An alert that reads “CPU > 80% for 5 mins” is considered noisy because:

• It wakes up engineers unnecessarily

• It doesn’t tie to user impact

• It lacks context

• All of the above