This plan is designed for candidates who want a repeatable structure: learn, drill, integrate, review.
How long should you study?
Typical candidates need 45-80 focused hours.
| Your time |
Recommended timeline |
| 12-15 hrs/week |
30 days (intensive) |
| 6-9 hrs/week |
60 days (balanced) |
| 3-5 hrs/week |
90 days (part-time) |
How to use this plan well
| If you are… |
Use the plan like this |
| strong on basic cloud concepts but weaker on OCI pathing |
spend extra time on VCN design, gateways, route tables, NSGs, and security lists |
| comfortable with networking but weaker on OCI governance |
spend extra time on tenancy, compartments, groups, dynamic groups, and policy scope |
| short on time |
complete one pass through governance, networking, placement, and resilience before chasing peripheral service detail |
How to use this plan
- treat the resources page as your official reference shelf
- send recurring misses to the local cheat sheet or glossary
- keep a mistake log for tenancy scope, network pathing, service placement, and resilience choices
30-Day Intensive Plan (4 weeks)
| Week |
Focus |
Output |
| 1 |
OCI core, governance, compartments, IAM, tagging, and encryption defaults |
drills |
| 2 |
networking design: VCN, subnets, routing, gateways, NSGs, and security lists |
drills |
| 3 |
compute, storage, database selection, and load-balancing patterns |
mixed sets |
| 4 |
HA basics, observability, and end-to-end review |
readiness check |
60-Day Balanced Plan (8 weeks)
| Week |
Focus |
| 1-2 |
OCI core and compartment or IAM strategy |
| 3-4 |
networking and connectivity concepts |
| 5 |
load balancing and DNS concepts |
| 6 |
compute, storage, and database selection |
| 7 |
HA basics, backups, and DR awareness |
| 8 |
mixed review and cheat-sheet revision |
90-Day Part-Time Plan (12 weeks)
| Weeks |
Focus |
| 1-3 |
core and governance |
| 4-6 |
networking and connectivity |
| 7-9 |
compute, storage, database, and load balancing |
| 10 |
observability and troubleshooting basics |
| 11-12 |
mixed review and final revision |
What strong prep usually does
- separates IAM choices from networking choices
- turns misses into short rules such as
a route table changes path, not permission
- practices public-edge and private-tier placement repeatedly until it stops feeling fuzzy
- keeps associate-level answers clean instead of reaching for professional-level complexity
If your misses cluster, route them deliberately
| Miss pattern |
Usually means |
Best page to revisit |
| you keep mixing IAM and network controls |
your OCI control boundaries are still fuzzy |
Glossary |
| pathing answers still feel interchangeable |
you need a stronger model of gateways, routes, and subnet placement |
Cheat Sheet |
| service choices still all sound plausible |
you need a cleaner OCI service map |
FAQ |
| Oracle terminology still feels vague |
you need to revisit the official OCI docs through the Resources page |
Resources |
Booking signal
Book when you can:
- explain which control belongs to IAM, compartments, or networking without mixing them
- place public edge, private application, and private data tiers cleanly
- choose between OCI service options with a clear reason tied to architecture needs
- reason about HA, backups, and recovery without defaulting to overbuilt answers
Final 72 hours
- re-read Cheat Sheet for networking, service selection, and architecture traps
- use FAQ to clean up final uncertainty
- keep Resources open for exact OCI behavior or service details