Updated recently
Last updated:
Quick Answer: this six-week SailPoint IIQ study plan assumes 8–10 hours per week and one persistent lab. Weeks 1–2 build directory and identity foundations, weeks 3–4 cover core IIQ operations (aggregation, correlation, provisioning), and weeks 5–6 finish BeanShell, workflows and a small end-to-end project you can show in interviews. Each week ends with a checkpoint you either pass or repeat — moving on with a failed checkpoint is how study plans die in week four.
Who This Plan Is For (and Who Should Skip It)
This schedule suits freshers and career switchers starting from directory basics. If you already administer Active Directory and script in Java or Python, compress weeks 1–2 into three days and finish in four weeks. If you cannot commit 8 hours a week, stretch every week to a week and a half — the order matters more than the speed.
Week 1: Directories and the Idea of Identity
| Day | Task |
|---|---|
| Day 1–2 | Active Directory fundamentals: users, groups, OUs, domains. Install ADUC views or use a free online AD lab to browse objects. |
| Day 3 | LDAP concepts: DNs, attributes, filters. Practise reading a DN aloud and predicting a filter result. |
| Day 4–5 | Identity governance concepts: identity vs account vs entitlement, JML, provisioning vs deprovisioning. Read the IGA fundamentals guide. |
| Day 6 | Write a one-page summary: “how access flows from HR hire to Active Directory account in a company without IIQ.” The pain you describe is what IIQ solves. |
| Day 7 | Rest or catch-up. |
Checkpoint: you can explain, without notes, what breaks in a company with 200 apps when an employee is terminated and no deprovisioning process exists.
Week 2: Meet IdentityIQ
| Day | Task |
|---|---|
| Day 1–2 | Get lab access (training provider or cloud trial). Log in, tour the UI: Identities, Applications, Tasks, Certifications, Reports. |
| Day 3–4 | Study the object model: identity, link, account, application, schema. Work through the beginner IIQ tutorial hands-on. |
| Day 5 | Read the IIQ architecture breakdown; label the console, database, connectors and IQService on a whiteboard from memory. |
| Day 6–7 | Create a test application definition against a flat-file or database connector. First aggregation run. Break something on purpose; find it in the task result. |
Checkpoint: you completed one aggregation and can say exactly where the collected accounts landed and what correlation has not done yet.
Week 3: Aggregation, Correlation, Refresh
| Day | Task |
|---|---|
| Day 1–2 | Run full vs delta aggregations on your test application. Compare task timings and results. |
| Day 3–4 | Configure correlation: first with built-in matching, then with a custom rule. Create deliberate duplicates and watch them correlate or quarantine. |
| Day 5 | Identity refresh: identity attributes, mapping an attribute from the HR feed. Observe what refresh recalculates and what it does not. |
| Day 6 | Break correlation on purpose (bad rule, wrong attribute). Practise debugging from the task result back to the rule. |
| Day 7 | Checkpoint review. |
Checkpoint: given a freshly imported account that failed to correlate, you can name three probable causes and test each in under 15 minutes.
Week 4: Provisioning
| Day | Task |
|---|---|
| Day 1–2 | Provisioning policies: create, fields, defaults. Provision a test account through a request or role. |
| Day 3 | Provisioning plans: preview a plan before execution; read every XML element in it. |
| Day 4 | IQService: understand its role for AD operations; practise with the connector documentation open beside you. |
| Day 5–6 | End-to-end: request an entitlement, approve it, watch the plan execute, verify on the target, check the identity snapshot updated. |
| Day 7 | Write the flow as a numbered runbook — this becomes interview material. |
Checkpoint: you can narrate the full request-to-provisioned flow including where it can fail, which is exactly what the identity request lifecycle guide formalises.
Week 5: BeanShell and Workflows
| Day | Task |
|---|---|
| Day 1–2 | BeanShell fundamentals: objects, collections, null checks. Work through 5 of the 10 BeanShell rule examples in the lab. |
| Day 3–4 | Workflows: open a stock workflow XML, trace it step by step. Then the workflow examples: build a two-step approval. |
| Day 5 | Lifecycle events: configure a create-event handler; observe it fire when a test identity appears. |
| Day 6 | Rule debugging: inject a failure, read the stack trace, fix it. Repeat twice. |
| Day 7 | Checkpoint review. |
Checkpoint: you can read an unfamiliar rule and identify what it changes, what it assumes, and where it throws on null input.
Week 6: Project, Certification Decision, Interview Prep
| Day | Task |
|---|---|
| Day 1–3 | Mini project: onboard a mock HR feed, configure correlation, enable birthright provisioning into a test directory, run one certification campaign. Screenshot every stage. |
| Day 4 | Write the two-page project summary (problem, design, bugs hit, fixes). This is the portfolio artefact. |
| Day 5 | Run the IIQ mock test; target 80%+. |
| Day 6 | Practise 10 answers aloud from the IIQ interview questions guide, including two scenario answers. |
| Day 7 | Decide on the certification exam using the certification cost and path guide. Book only if week-6 scores were honest. |
If You Fall Behind in Week Three
Almost everyone slips somewhere in weeks 3–4, when theory meets real task debugging. The recovery rule: do not compress later weeks to catch up — repeat the failed week instead, at 6 hours instead of 10, and move its checkpoint. A plan finished in eight honest weeks beats a six-week plan abandoned in week four, which is the fate of most schedules of this type. Track one line per day in your notebook: what you ran, what broke, what fixed it. When motivation dips — it will, around week four — the notebook itself becomes the evidence that you are progressing, and that evidence is what carries you through. Book your lab hours in your calendar like meetings; plans that rely on spare time dissolve.
Study-Plan Traps That Waste Months
- Tutorial watching as progress. Videos feel productive; labs are what stick. Cap video time at one third of your hours.
- Skipping checkpoints. Every unchecked checkpoint resurfaces as an interview question you cannot answer.
- Collecting materials. Three PDFs and one lab beat thirty bookmarks. Close the tabs.
Training Resources
If self-study stalls in week 3 — the most common stall point — the SailPoint IdentityIQ Certification Training provides instructor-led labs, checkpoints with real review, and a capstone project that replaces week 6. The SailPoint IdentityIQ roadmap shows what comes after week 6, and the IAM training track widens the lens to the full domain.
FAQ
Can I learn SailPoint IIQ in 6 weeks?
You can reach genuine beginner-plus level in six weeks at 8–10 hours weekly with lab access: able to onboard an application, configure correlation and provisioning, and pass a mock test at 80%. Interview-ready depth typically needs another 4–8 weeks of practice or project work.
How many hours per week for the SailPoint IIQ study plan?
8–10 hours is the honest minimum: 2–3 hours of concept reading, the rest in the lab. Under 6 hours a week, stretch the plan to 9–10 weeks rather than skipping checkpoints.
Do I need a paid lab to follow this plan?
Yes, realistically. IIQ is a licensed product, so you need a training provider’s lab or an authorised trial. Week 1–2 theory works with free material, but from week 3 onward the plan fails without hands-on IIQ access.
Should I take the certification right after the 6 weeks?
Book it only if your mock tests consistently score 80%+ and your project is complete. The exam costs roughly ₹25,000–₹28,000 in India; our certification guide explains when it pays off versus when practice time is the better spend.
What if I already know Active Directory and scripting?
Compress weeks 1–2 into two or three days and start week 3 immediately. Experienced AD admins commonly finish this plan in four weeks and use the extra time on workflow customisation, which is where billable depth lives.
