This plan is built around the OCI developer decision loop: authenticate -> classify interaction -> choose execution boundary -> make retry safe.
How to use this plan well
Each study block should do four things:
- classify the question as identity, interaction, execution, or reliability
- choose the OCI control or service that belongs there
- do a short scenario set
- write down whether the miss was wrong boundary choice or weak retry or auth reasoning
flowchart LR
Classify["Classify identity / interaction / execution / reliability"] --> Choose["Choose OCI control or service"]
Choose --> Drill["Do short scenario set"]
Drill --> Review["Review why misses happened"]
Review --> Classify
How long should you study?
Typical candidates need 65 to 115 focused hours.
| Your time |
Recommended timeline |
Good fit |
| 18 to 22 hrs/week |
30 days |
intensive path with recent OCI developer work |
| 10 to 14 hrs/week |
60 days |
balanced path for most candidates |
| 6 to 9 hrs/week |
90 days |
part-time path with slower reinforcement |
30-day intensive plan
| Week |
Focus |
Output |
| 1 |
user keys, instance principals, resource principals, IAM, and compartment scope |
auth confusion sheet and short drills |
| 2 |
API Gateway, SDK or CLI behavior, and synchronous request flow |
ingress and execution tie-break notes |
| 3 |
Functions, Events, Notifications, Streaming, and async routing |
interaction-lane notes and mixed sets |
| 4 |
retry safety, idempotency, logging, and final review |
mixed sets and compression |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
auth patterns and least-privilege boundaries |
| 2 |
3 to 4 |
API Gateway, SDK or CLI, and resource interaction logic |
| 3 |
5 to 6 |
Functions, events, notifications, streaming, and async service fit |
| 4 |
7 |
retry, idempotency, logging, and failure-path reasoning |
| 5 |
8 |
weak-lane repair and mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
identity and service-boundary vocabulary |
stop losing points to auth and scope confusion |
| 2 |
request flow, async routing, and execution choices |
get stronger at service-fit judgment |
| 3 |
retry safety, observability, and exam tie-breaks |
finish with mixed-set confidence |
If misses cluster here, do this next
| Miss pattern |
Weak lane |
Fix next |
| you keep picking the wrong credential model |
identity |
review user API keys vs instance principals vs resource principals |
| you keep choosing the wrong service for the request path |
interaction |
review API Gateway vs Events vs Notifications vs Streaming |
| you use one service as the answer to every problem |
execution boundary |
review ingress, handler, consumer, and orchestration responsibilities |
| you ignore duplicate delivery or replay risk |
reliability |
review retry, backoff, and idempotent handler design |
What strong prep usually does
- classifies the problem before naming the service
- keeps short confusion tables for API Gateway vs Functions, Events vs Notifications, and retry vs idempotency
- writes down why the winning answer is safer or more repeatable instead of only memorizing product names
- uses Oracle docs to settle disagreements, then comes back here for compression
Final 72 hours
| Keep doing |
Stop doing |
| rereading the cheat sheet and glossary |
opening unrelated new OCI services |
| reviewing auth and async-boundary misses |
treating every event or async service as equivalent |
| checking official docs for disputed behavior |
building a large late-stage developer platform |
| practicing identity -> interaction -> execution -> reliability order |
trusting unsupported community summaries over Oracle docs |
Route yourself well
- API, event, and retry traps: Cheat Sheet
- high-confusion developer terms: Glossary
- last-week questions: FAQ
- official Oracle and OCI source routing: Resources