This plan is built around the autonomous-database loop: choose provisioning boundary -> harden access -> observe workload -> prove recovery.
How to use this plan well
Each study block should do four things:
- classify the scenario as provisioning, security, performance, or recovery
- choose the Oracle control or service boundary that belongs there
- do a short scenario set
- write down whether the miss came from wrong boundary choice, weak audit or network reasoning, or confused recovery language
flowchart LR
Classify["Classify provisioning / security / performance / recovery"] --> Choose["Choose Oracle control or boundary"]
Choose --> 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 recent Oracle database operations 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 |
provisioning models, service options, and management boundaries |
provisioning notes and drills |
| 2 |
security, networking, auditing, keys, and access boundaries |
security tie-break sheet |
| 3 |
performance, scaling, monitoring, and troubleshooting |
weak-lane notes and mixed sets |
| 4 |
backup, recovery, continuity, and operational readiness |
mixed review and readiness check |
60-day balanced plan
| Phase |
Weeks |
Focus |
| 1 |
1 to 2 |
provisioning choices and service boundaries |
| 2 |
3 to 4 |
security, connectivity, audit, and keys |
| 3 |
5 to 6 |
workload observation, tuning, scaling, and troubleshooting |
| 4 |
7 |
backup, restore, recovery, and readiness |
| 5 |
8 |
weak-lane repair and mixed review |
90-day part-time plan
| Month |
Focus |
Goal |
| 1 |
provisioning and service-option vocabulary |
stop losing points to boundary confusion |
| 2 |
security and performance behavior |
get stronger at safe-default choices |
| 3 |
recovery, troubleshooting, and exam 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 deployment model |
provisioning |
review serverless, dedicated, and managed-boundary differences |
| you assume managed means secure enough |
security |
review private access, least privilege, audit, and key control |
| you always answer with scale |
performance |
review workload shape, tuning, concurrency, and monitoring before capacity increases |
| you mention backups without proving recoverability |
recovery |
review restore, continuity, runbooks, and ownership |
What strong prep usually does
- classifies the scenario before naming a feature
- keeps a short confusion table for serverless vs dedicated, auditability vs observability, and backup vs recovery plan
- writes down what the team still owns even on a managed platform
- uses Oracle docs to settle disputed boundaries, then comes back here for compression
Final 72 hours
| Keep doing |
Stop doing |
| rereading the cheat sheet and glossary |
opening unrelated new Oracle services |
| reviewing security, recovery, and audit misses |
treating managed automation as zero-ops |
| checking Oracle docs for disputed boundaries |
chasing scaling answers before checking workload and exposure |
| practicing provisioning -> security -> performance -> recovery order |
trusting unsupported community summaries over Oracle docs |
Route yourself well