Skip to content
IT Canvass
Practice · Lesson

Cheat sheets

Quick answer

Cheat sheets condense the details you look up constantly into printable one-pagers: rule types and their inputs, iiq console commands, the core object types, and the aggregation-to-provisioning lifecycle. Use them for quick recall during work, interviews and exams.

Key takeaways

  • Printable one-page quick references
  • Rule types and their inputs
  • iiq console commands
  • Core object types at a glance
  • The lifecycle summarised

Cheat sheets condense the SailPoint facts you reach for constantly, object names, common rule contexts, task types, API filter operators, key troubleshooting steps, into printable quick references you keep beside you while you work.

What a good cheat sheet captures

The value of a cheat sheet is speed of recall for things you use often but do not need to memorise perfectly: which object backs a role (Bundle), the operators in an API filter (eq, sw, co), the order of the provisioning flow, or the first thing to check when provisioning fails.

How to use them

  • Keep the relevant sheet open while building or debugging.
  • Print the ones you use daily.
  • Treat them as a memory aid, not a substitute for understanding the concept.

Suggested sheets

  • Object model at a glance (Identity, Link, Bundle, ManagedAttribute).
  • Rule types and their contexts.
  • API filter and pagination syntax.
  • Troubleshooting first-steps by symptom.

Common pitfalls

  • Relying on a cheat sheet without the underlying concept.
  • Using an outdated sheet that no longer matches your version.
  • Cramming too much onto one sheet so nothing stands out.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

Check your understanding

  1. Cheat sheets are for?

    • A. Quick recall. They condense details for recall once you know the concept.
    • B. export. iiq console export writes objects to a file.
    • C. context, account, application. Correlation receives context, account and application.
    Show answer

    A. Quick recall. They condense details for recall once you know the concept.

    Quick recall. They condense details for recall once you know the concept.

  2. A correlation rule's inputs include?

    • A. Quick recall. They condense details for recall once you know the concept.
    • B. context, account, application. Correlation receives context, account and application.
    • C. export. iiq console export writes objects to a file.
    Show answer

    B. context, account, application. Correlation receives context, account and application.

    context, account, application. Correlation receives context, account and application.

  3. The console command to export objects is?

    • A. context, account, application. Correlation receives context, account and application.
    • B. Quick recall. They condense details for recall once you know the concept.
    • C. export. iiq console export writes objects to a file.
    Show answer

    C. export. iiq console export writes objects to a file.

    export. iiq console export writes objects to a file.

Frequently asked questions

What does the term cheat sheets refer to in SailPoint?

Cheat sheets condense the SailPoint facts you reach for constantly, object names, common rule contexts, task types, API filter operators, key troubleshooting steps, into printable quick references you keep beside you while you work.

What is another point to note about cheat sheets?

The value of a cheat sheet is speed of recall for things you use often but do not need to memorise perfectly: which object backs a role (Bundle), the operators in an API filter (eq, sw, co), the order of the provisioning flow, or the first thing to check when provisioning fails.

What else is worth knowing about cheat sheets?

Keep the relevant sheet open while building or debugging. Print the ones you use daily. Treat them as a memory aid, not a substitute for understanding the concept.

What tends to go wrong with cheat sheets?

Relying on a cheat sheet without the underlying concept. Using an outdated sheet that no longer matches your version. Cramming too much onto one sheet so nothing stands out.
CallWhatsAppEnquire