Oracle Database@AWS Architect Professional study plan
Oracle Database@AWS Architect Professional · Give each week a clear focus.
8 weeks · About 7 hours per week
Oracle Database@AWS Architecture and Solution Design
Map every component of the Oracle Database@AWS reference architecture (ODB network, VPC peering, Exadata infrastructure, VM cluster, container database, pluggable databases) into a single labeled diagram you draw from memory
Explain out loud, in under five minutes, how OCI-hosted Exadata hardware is presented inside an AWS account and which party owns each layer of the stack
Compare Oracle Database@AWS with self-managed RDS for Oracle and with running Oracle on EC2, listing at least six decision criteria such as latency, licensing, and operational ownership
Identify the shared-responsibility split for patching, backups, network controls, and identity, and record it in a table
Your checkpoint
A one-page architecture diagram plus a shared-responsibility table covering at least 12 components, reviewed against official Oracle and AWS documentation
Oracle Database@AWS Architecture and Solution Design
Design two candidate solutions for a given workload (one latency-sensitive OLTP, one consolidation/DR scenario) and justify the choice of Exadata shape, storage, and availability domain placement
Calculate capacity and licensing implications for a stated workload, including core counts, storage headroom, and the effect of Auto Scaling or elastic configuration where available
Draft a migration-readiness and sizing checklist that a customer would complete before committing to a design
Present a 10-minute design review to a peer or rubber-duck recording, defending trade-offs on cost, resilience, and complexity
Your checkpoint
A written solution design document (2-3 pages) for one scenario, including sizing rationale, HA topology, and a risk list
Oracle Database@AWS Provisioning, Deployment, and Configuration
Write a step-by-step provisioning runbook covering prerequisites, IAM permissions, ODB network creation, Exadata infrastructure, VM cluster, and CDB/PDB creation
List the exact order of operations and the failure modes that occur when steps are performed out of order
Enumerate the configuration parameters that most affect performance and availability, and state a recommended default for each
Document how to validate a completed deployment with connectivity, listener, and database health checks
Your checkpoint
A provisioning runbook of at least 20 numbered steps with a validation checklist and rollback notes
Oracle Database@AWS Provisioning, Deployment, and Configuration & Oracle Database@AWS Architecture and Solution Design
Automate a repeatable deployment using infrastructure-as-code or CLI scripting, parameterizing network CIDRs, credentials references, and cluster sizing
Tear down and rebuild the environment at least once to prove the automation is idempotent and complete
Reconcile your runbook against the automation and correct every discrepancy
Review the domain 1 and 2 objectives and rewrite your notes into question-and-answer form for self-testing
Your checkpoint
A working, re-runnable deployment script or template stored in version control, plus a corrected runbook
Oracle Database@AWS Networking, Security, and Identity
Design the network topology end to end: VPC and subnet layout, ODB network peering, route tables, security groups, and DNS resolution paths between AWS and the database
Trace a client connection hop by hop and identify every control point where traffic could be blocked
Define an identity model covering AWS IAM principals, Oracle Cloud Identity, database users, and how federated access is granted and audited
Specify encryption in transit and at rest, key management, and audit logging destinations, then verify each control is configurable
Your checkpoint
A network and identity design package: topology diagram, connection trace table, IAM/identity matrix, and control-to-configuration mapping
Oracle Database@AWS Networking, Security, and Identity & Oracle Database@AWS Operations, High Availability, and Migration
Implement and test least-privilege access for three personas (DBA, application, auditor), proving each can do its job and nothing more
Configure and verify audit logging and alerting, then confirm logs reach the intended destination with the expected retention
Document a break-glass procedure for emergency access including approval, time limits, and review
Run a connectivity failure test (blocked route or security group change) and record detection and recovery time
Your checkpoint
A security validation report with test evidence for each persona, log verification, and one failure-injection result
Oracle Database@AWS Operations, High Availability, and Migration
Define recovery objectives (RPO/RTO) for a stated business case and select the matching HA and DR pattern, including Data Guard or backup-based strategies
Write and execute a backup and restore test, measuring actual restore time and data loss against the stated objectives
Document patching, scaling, and maintenance workflows including who initiates them and what the expected impact is
Build a monitoring plan covering database, host, and network metrics with thresholds and escalation paths
Your checkpoint
An operations runbook plus a restore test record showing measured RTO/RPO against targets
Oracle Database@AWS Operations, High Availability, and Migration & Oracle Database@AWS Architecture and Solution Design
Produce a migration plan for one workload using a phased cutover, including assessment, data movement method, validation, and rollback triggers
Complete two timed practice exams or a large self-written question set covering all four domains, and score above 80 percent
Review every missed item and write a one-line correction for each into a personal error log
Re-read only the highest-risk notes and confirm each domain's objectives are covered by your materials
Your checkpoint
A migration plan plus a scored practice result above 80 percent with an error log of corrections
Milestones
Week 2: You can draw the full architecture from memory and defend one written design against cost and resilience objections
Week 4: You can provision a complete environment from your own automation and have rebuilt it once without manual fixes
Week 6: You can trace any client connection to the database, name every control point, and prove least privilege for three personas
Week 8: You have a measured restore test meeting stated RTO/RPO and score above 80 percent on a full-domain practice set