This exam is scenario-heavy. Build architecture instincts around failure, security, boundaries, and operations instead of trying to memorize product lists.
How to use this plan well
Each study block should do four things:
- classify the scenario as continuity, boundary, control, operability, or service-fit
- decide which OCI design pattern belongs there
- do a short scenario set
- write down whether the miss was overbuilding, undercontrolling, or weak recovery logic
flowchart LR
Classify["Classify continuity / boundary / control / operability"] --> Pattern["Choose OCI design pattern"]
Pattern --> Drill["Do short scenario set"]
Drill --> Review["Review why misses happened"]
Review --> Classify
How long should you study?
Typical candidates need 80 to 140 focused hours.
| Your time |
Recommended timeline |
Good fit |
| 18 to 22 hrs/week |
30 days |
intensive path with prior OCI or architecture experience |
| 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 |
governance, IAM, compartments, and control-plane thinking |
architecture-rule notes and short drills |
| 2 |
advanced networking, hybrid connectivity, and boundary design |
network and boundary tie-break sheet |
| 3 |
HA, DR, backups, replication, RTO, and RPO |
continuity notes and mixed sets |
| 4 |
security architecture, operability, automation, and final readiness |
mixed sets and compression |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
terminology cleanup and architecture-lane classification |
| 2 |
3 to 4 |
governance, IAM, compartments, and control patterns |
| 3 |
5 to 6 |
advanced networking, hybrid connectivity, and path design |
| 4 |
7 to 8 |
HA, DR, backup, replication, and continuity targets |
| 5 |
9 |
service fit, automation, and observability |
| 6 |
10 |
weak-lane repair and final mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
governance, IAM, and boundary vocabulary |
stop losing points to control confusion |
| 2 |
networking, continuity, and service-fit trade-offs |
build stronger architect-level judgment |
| 3 |
operability, automation, and final tie-breaks |
finish with mixed-set confidence |
If misses cluster here, do this next
| Miss pattern |
Weak lane |
Fix next |
| you choose continuity patterns that do not match the target |
continuity |
review HA vs DR, RTO, RPO, backup, and failover |
| you design with boundaries that are too broad or too weak |
boundary design |
review compartments, VCNs, subnets, and edge separation |
| you pick strong services but poor controls |
security and control |
review IAM, keys, audit, and network controls |
| you solve deployment-day needs but not day-2 operations |
operability |
review observability, automation, rollback, and repeatability |
What strong prep usually does
- classifies the lane first, then chooses the pattern
- keeps a short confusion list for HA vs DR, backup vs replication, and control plane vs data plane
- writes down why the winning answer reduces blast radius or simplifies recovery instead of just memorizing it
- 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 weak-lane misses |
treating every scenario like a feature checklist |
| checking official docs for disputed boundaries |
building a large new architecture lab late |
| practicing continuity vs boundary vs control vs operability classification |
trusting unsupported summary sheets over Oracle docs |
Route yourself well
- architecture, HA, and DR traps: Cheat Sheet
- high-confusion professional-level terms: Glossary
- last-week questions: FAQ
- official Oracle and OCI source routing: Resources