PogoIAM

Free lesson 1 · JumpCloud · Advanced prep

Diagnose a directory sync mismatch

Practice at Gulfpoint Design Studio, a fictional workplace.

Learn the basics

How the cloud works. A cloud directory connects people to devices, applications, and network resources.

JumpCloud can connect to supported external directories and HR systems. The direction, authoritative attributes, and identity matching depend on the connector. An event marked successful may still need a downstream record comparison.

Vendor documentation

Try the lab

Two studio pilot workers have mismatched attributes between JumpCloud and their approved cloud directory. Review source ownership, scope, and matching. Compare one unaffected record and decide whether a retry is justified.

Source ownership
Matching evidence
Scope check
Error isolation
Retry and handoff

Check your understanding

Why check the specific integration type first?
A record exists downstream with the expected name but wrong attributes. What comes next?
What can a healthy source connector leave unresolved?
When is an expanded pilot justified?
What belongs in a sync handoff?
Which source ownership choice meets this ticket?
Which matching evidence choice meets this ticket?
Which scope check choice meets this ticket?
Which error isolation choice meets this ticket?
Which retry and handoff choice meets this ticket?
Which evidence directly verifies this ticket’s “Source ownership” decision?
Which evidence directly verifies this ticket’s “Matching evidence” decision?
Which evidence directly verifies this ticket’s “Scope check” decision?
Which evidence directly verifies this ticket’s “Error isolation” decision?
Which evidence directly verifies this ticket’s “Retry and handoff” decision?

Continue learning

The first lesson is free. The remaining lessons, final assessment and completion certificate are part of the full course.

See planned course access