Most candidates pass with 70 to 140 focused hours depending on prior network and OCI experience. The best use of time is to study by path type and control boundary, not by memorizing disconnected gateway names.
How to use this plan well
Each study block should do four things:
- classify the issue as path, filter, private connectivity, DNS, or distribution
- decide which boundary or control belongs there
- do a short scenario set
- write down whether the miss was route logic, filter scope, or troubleshooting order
flowchart LR
Classify["Classify path / filter / DNS / distribution"] --> Choose["Choose boundary or control"]
Choose --> Drill["Do short scenario set"]
Drill --> Review["Review why misses happened"]
Review --> Classify
How long should you study?
| Your time |
Recommended timeline |
Good fit |
| 18 to 22 hrs/week |
30 days |
intensive path with some networking 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 |
VCNs, subnets, route tables, and basic path logic |
route-choice notes and short drills |
| 2 |
NSGs, security lists, gateways, and edge-exposure control |
path-vs-filter tie-break sheet |
| 3 |
DRG, VPN, FastConnect, and private connectivity design |
weak-lane notes and mixed sets |
| 4 |
DNS, load balancing, troubleshooting order, and final readiness |
mixed sets and compression |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
terminology cleanup and path classification |
| 2 |
3 to 4 |
routing, subnets, gateways, and edge logic |
| 3 |
5 to 6 |
NSGs, security lists, firewall boundaries, and segmentation |
| 4 |
7 |
DRG, VPN, FastConnect, and hybrid reachability |
| 5 |
8 |
DNS, load balancing, and troubleshooting flow |
| 6 |
9 to 10 |
weak-lane repair and final mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
core networking vocabulary and path logic |
stop losing points to route-versus-filter blur |
| 2 |
private connectivity, segmentation, and troubleshooting |
build stronger boundary judgment |
| 3 |
DNS, traffic distribution, 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 choosing the wrong gateway or route |
path construction |
review internet, NAT, service gateway, DRG, VPN, and FastConnect roles |
| you know the path but choose the wrong rule scope |
filtering |
review NSGs, security lists, and least-privilege boundaries |
| you confuse hybrid-connectivity options |
private connectivity |
review DRG, VPN, FastConnect, and attachment purpose |
| you skip DNS or troubleshooting order |
diagnosis flow |
review resolve, route, filter, then gateway or attachment state |
What strong prep usually does
- classifies the question as path, filter, DNS, or distribution before choosing a tool
- keeps a short confusion list for route table vs NSG and NAT vs service gateway
- writes down why the winning answer is narrower or cleaner 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 networking services |
| reviewing weak-lane misses |
treating every failure like a firewall problem |
| checking official docs for disputed boundaries |
building a large new network lab late |
| practicing path and troubleshooting order |
trusting unsupported diagrams over Oracle docs |
Route yourself well
- path-selection and control-placement traps: Cheat Sheet
- high-confusion networking terms: Glossary
- last-week questions: FAQ
- official Oracle and OCI source routing: Resources