Connect | Skill Check Quiz

Connect Cross-Service Decision Drill

Status: Not Started | Pass threshold: 85% | Points: 155

L3 25 min

Best score

Attempts

Pass rate

Passed

Module Navigator

CON-LAB-03: Connect Lab 03 Consumer Latency

Mock Investigation Lab

Review Prior Module ←

Recommended Next

Connect Service Topology

Reading Module

Resume Recommended Path →

Connect Capstone War Room

Mock Investigation Lab

Continue To Next Module →

Learning Guidance

Objectives

Make escalation decisions with incomplete but sufficient evidence.
Identify dependency-driven symptoms versus owning-service failures.

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 →

01KJ1EGNR2JP3C9SJNYFA32X3Q

2/22/2026 | n/a

medium

PH US Pick Up Order Flow 2 synthetic test failed on Pizza Hut website

This browser synthetic test is basic. It tests for basic user functionality on Pizza Hut's website and refreshes orders on Customer Support with default filt...

commerce Root cause (deployment) aligns with L3 focus

Study Incident →

Skill Check

0/5 answered

Assessment Navigator

0 of 5 answered

Question 1 of 5

Q1. Advanced: 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.