Connect | Skill Check Quiz

Connect Core Signal Pattern Check

Status: Not Started | Pass threshold: 80% | Points: 130

L2 20 min

Best score

Attempts

Pass rate

Passed

Module Navigator

Runbook: Switchboard Dispatch Failures

Reading Module

Review Prior Module ←

Recommended Next

Connect Service Topology

Reading Module

Resume Recommended Path →

CON-LAB-01: Connect Lab 01 Switchboard

Mock Investigation Lab

Continue To Next Module →

Learning Guidance

Objectives

Classify alert pattern type and likely owner.
Separate symptom noise from actionable customer impact.

Source Artifacts

Internal source references are available for maintainers but are not exposed in deployed environments.

Field Evidence

Real incidents related to what you're learning.

01KJ45E02K07DCN4KAZGGC2SCA

2/23/2026 | n/a

high

Switchboard unable to dispatch events to KFC US endpoints in production

• Org: kfc_us • Env: production • Service: switchboardserviceretry1m ## Key Information: > • Switchboard is unable to dispatch events to kfc_us > > • This er...

connect Same product lane: connect

Study Incident →

01KJ0M5JDDZ0MEES932WA0C6G9

2/21/2026 | n/a

medium

Increased rate of stores marked OFFLINE in Olympus due to connection instability

• Org: tb_uk • Env: prod-hopper • Service: olympus-daemons ## Key Information: > This monitor tracks when a store status has successfully change to OFFLINE i...

connect Same product lane: connect

Study Incident →

01KJ37K5MPZ9FT4HCY81N92VPE

2/22/2026 | n/a

medium

Container forcibly terminated due to out of memory in backend-users-deployment-green pod

• Org: • Env: prod • Service: A container in prod was forcibly terminated • indicates either a memory leak or insufficient memory limit • engage on-call SRE ...

shared Root cause (data) aligns with L2 focus

Study Incident →

Skill Check

0/5 answered

Assessment Navigator

0 of 5 answered

Question 1 of 5

Q1. measure latency trend and backlog behavior

easy byte-connect, switchboard-triage

Use monitor scope and impact evidence before routing.

measure latency trend and backlog behavior Escalate immediately without verifying blast radius. Wait for potential auto-recovery before collecting evidence.