Multicloud work is boundary-heavy. Study by decision lane, not by trying to memorize every provider feature in one pass.
How to use this plan well
Each study block should do four things:
- review one multicloud lane
- work a small scenario set
- write down why the winning answer was stronger
- route misses into the next block instead of just rereading everything
flowchart LR
Read["Read one lane"] --> Drill["Do scenario set"]
Drill --> Review["Review why misses happened"]
Review --> Route["Route misses by lane"]
Route --> Read
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 reset or recent cloud 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 |
OCI foundation refresh, compartments, IAM, landing-zone thinking |
trust-boundary notes and short scenario drills |
| 2 |
VPN, FastConnect, route design, segmentation, exposure control |
connectivity comparison sheet |
| 3 |
data locality, sovereignty, replication, workload placement |
data-placement tie-break notes |
| 4 |
resilience, monitoring ownership, audit, recovery plans, final compression |
mixed sets and last-week review |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
OCI refresh and terminology cleanup |
| 2 |
3 to 4 |
identity, trust, compartments, and policy scope |
| 3 |
5 to 6 |
connectivity, routing, private path choices |
| 4 |
7 |
data placement, egress, sovereignty, replication |
| 5 |
8 |
resilience, recovery, monitoring, and audit |
| 6 |
9 |
weak-lane repair |
| 7 |
10 |
mixed timed sets and compression |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
OCI basics plus multicloud vocabulary |
stop losing points to terminology blur |
| 2 |
trust, connectivity, and placement |
make the main architecture lanes explicit |
| 3 |
resilience, operations, and exam-style 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 trust or permission boundary |
identity |
review federation, least privilege, and auditability |
| you pick a connection without failure-path thinking |
connectivity |
review VPN, FastConnect, route tables, and segmentation |
| you move too much data or ignore locality |
data |
review sovereignty, replication, and egress trade-offs |
| you assume failover without proving operations ownership |
resilience and ops |
review recovery objectives, monitoring, and runbooks |
What strong prep usually does
- studies by boundary type, not by memorizing provider catalogs
- writes down why the winning answer was safer, narrower, or easier to operate
- keeps one short list of confused pairs and rereads it before each mixed set
- uses official Oracle and OCI docs to settle disagreements, then returns here for compression
Final 72 hours
| Keep doing |
Stop doing |
| review weak-lane notes and confused pairs |
building new large labs |
| reread the cheat sheet, glossary, and FAQ |
opening unrelated OCI services |
| practice short scenario classification |
treating the exam like a fundamentals memorization test |
| verify the official exam page and primary docs |
trusting stale third-party summaries over Oracle |
Route yourself well