1Z0-997-25 OCI Architect Professional
A structured, learner-friendly pathway through Oracle Cloud Infrastructure 2025 Architect Professional preparation, covering enterprise landing zones, cloud-native solution design, networking, high availability, disaster recovery, security, databases, multi-cloud and hybrid architecture, migration, observability, operations, and cost optimization.
Course coverage
What You Will Cover for 1Z0-997-25
Prepare for 1Z0-997-25 through 10 clear OCI architecture domains arranged for focused revision. You will move through landing zones, cloud-native platforms, enterprise networking, availability, disaster recovery, security, databases, multi-cloud and hybrid architecture, migration, observability, operations, and cost control in a practical sequence.
Move between landing zone, network, security, database, migration, and operations topics during revision so the architecture decisions connect naturally across an enterprise OCI environment.
OCI Professional Architecture Mindset and Landing Zone Design
Design OCI landing zones with the judgement expected of a professional cloud architect. You will connect tenancy structure, compartments, governance, operational standards, reference architectures, and cost controls into a coherent enterprise foundation.
- Design production landing zones that support enterprise security, operations, networking, and compliance needs from the first deployment stage.
- Evaluate tenancy layout decisions, including enterprise boundaries, shared-services placement, environment separation, and long-term scalability.
- Plan compartment models around business units, applications, environments, and policy scoping so teams can work safely without excessive privilege.
- Use resource tagging strategies for ownership, cost centre, environment, compliance classification, chargeback, and operational accountability.
- Apply baseline guardrails such as least privilege, standard architecture patterns, logging, monitoring, and controlled resource placement.
- Interpret cost governance requirements through budgets, usage visibility, tag-based reporting, and architecture choices that avoid unnecessary spend.
- Use OCI reference architecture thinking to balance simplicity, resilience, security, maintainability, and cost for multi-tier enterprise workloads.
- Recognize when governance must be centralized and when application teams need delegated control within approved architectural boundaries.
- Connect landing zone design to later decisions around networking, identity, databases, disaster recovery, observability, and automation.
- Prepare for exam scenarios where the best answer is the architecture that fits organizational constraints, not simply the most feature-rich option.
Architecting Cloud-Native Solutions on OCI
Strengthen your ability to design OCI cloud-native platforms using microservices, containers, serverless functions, API Gateway, CI/CD alignment, and Infrastructure as Code. The focus is on practical architecture decisions rather than isolated service memorization.
- Evaluate microservices boundaries, scaling domains, ownership models, and deployment independence for OCI-based application platforms.
- Select containerization strategies that fit workload portability, operational maturity, release velocity, and platform management requirements.
- Connect DevOps practices to OCI architecture by considering CI/CD pipelines, release governance, approval flows, and rollback planning.
- Use serverless functions where event-driven execution, short-lived processing, and operational simplicity are stronger than always-on infrastructure.
- Design API Gateway patterns for routing, authentication placement, throttling, service exposure, and consistent front-door control.
- Apply Infrastructure as Code practices using reusable modules, variables, environment parity, reviewable plans, and controlled promotion between environments.
- Understand drift awareness, change control, rollback thinking, and the operational risks of manual configuration in professional architectures.
- Connect application architecture with observability, security, secret management, network isolation, and deployment repeatability.
- Identify tradeoffs between managed services, containers, serverless components, and traditional compute for real enterprise requirements.
- Use this section to prepare for scenario questions where OCI-native design must support scalability, reliability, security, and maintainable delivery.
Core OCI Networking for Enterprise Architectures
Build professional-level confidence in OCI networking by connecting VCN design, subnet placement, route control, secure egress, NSGs, security lists, segmentation, hybrid connectivity, and peering into one enterprise network architecture.
- Plan VCN and subnet architecture using CIDR ranges that support future growth, connectivity, segmentation, and route management.
- Differentiate public and private subnet placement decisions so workload exposure is controlled by architecture rather than convenience.
- Interpret route table intent, next-hop selection, route propagation awareness, and isolation boundaries across application tiers.
- Design secure outbound access for private workloads using controlled egress patterns rather than direct public exposure.
- Compare security lists and network security groups so network rules are enforced at the right level for maintainable segmentation.
- Use multi-tier network patterns that separate web, application, data, management, and shared-services layers with clear control points.
- Evaluate hybrid connectivity choices for on-premises to OCI integration, including routing, latency, resilience, and security inspection needs.
- Understand local and remote VCN peering patterns, route requirements, non-overlapping CIDR needs, and common design constraints.
- Connect enterprise networking with load balancing, DNS, private access, observability, security, and disaster recovery decisions.
- Prepare for questions where the correct network design depends on traffic flow, exposure control, growth planning, and operational troubleshooting.
High Availability Architecture and Fault Isolation
Learn how to design OCI workloads for availability by combining fault domains, availability domains, redundancy, health checks, load balancing, scaling choices, and capacity planning into architectures that can tolerate failure gracefully.
- Use fault domains and availability domains to reduce correlated failure risk and improve resilience across compute and application tiers.
- Design redundancy across compute, network, and data layers so a single component failure does not become a service outage.
- Choose between public and private load balancing patterns based on user access paths, internal service traffic, and security requirements.
- Define health-check behaviour that detects unhealthy backends accurately without creating unnecessary failover or false-positive events.
- Evaluate horizontal and vertical scaling decisions for workload demand, application statefulness, operational complexity, and cost.
- Plan autoscaling triggers, scaling limits, capacity buffers, and guardrails so elasticity supports stability rather than uncontrolled growth.
- Connect availability architecture to database design, network routing, application statelessness, and operational monitoring.
- Identify when high availability requires application redesign rather than simply adding more infrastructure components.
- Understand how maintenance windows, dependency failures, traffic distribution, and capacity assumptions affect real service continuity.
- Use this section to practise reasoning through scenarios where fault isolation, performance, cost, and reliability must be balanced.
Disaster Recovery Design and Cross-Region Strategy
Translate business recovery expectations into OCI technical designs. You will focus on RPO, RTO, backups, replication, cross-region architecture, active-active and active-passive tradeoffs, DR drills, and failover runbooks.
- Convert RPO and RTO requirements into practical choices for backup frequency, replication method, recovery automation, and workload placement.
- Design backup and restore strategies by identifying what must be protected, where backups should reside, and how recovery is validated.
- Compare active-active and active-passive disaster recovery patterns based on cost, complexity, data consistency, application readiness, and failover objectives.
- Select cross-region data replication approaches according to workload criticality, latency tolerance, regulatory boundaries, and recovery risk.
- Create operational runbooks that define roles, decision points, validation tasks, communication steps, and rollback procedures.
- Use DR drills to prove recoverability instead of assuming backups and replication automatically produce a working recovery plan.
- Understand failover and failback orchestration as controlled operational processes, not one-time technical switches.
- Connect disaster recovery to identity, DNS, network routing, database protection, application dependencies, and observability.
- Recognize architecture choices that reduce downtime but increase cost or operational complexity, and justify the best fit for the scenario.
- Prepare for exam questions where recovery design must satisfy business continuity requirements under realistic constraints.
Security Solutions and Secrets/Key Automation
Design OCI security with a professional security-first mindset. You will connect network isolation, least privilege, auditability, Vault, secrets management, key management, rotation, secure pipelines, and credential-safe automation.
- Design secure multi-tier architectures with network isolation, identity-aware access, controlled administration paths, and reduced public exposure.
- Apply least privilege consistently across users, groups, dynamic groups, policies, services, automation, and runtime workloads.
- Avoid hard-coded credentials by using identity-first access models, instance or resource principals, and controlled secret retrieval patterns.
- Use OCI security posture design principles around logging, alerting, auditability, evidence retention, and operational accountability.
- Implement and automate secrets management with OCI Vault while considering access control, lifecycle management, and leakage prevention.
- Evaluate customer-managed and provider-managed key decisions based on compliance, rotation, ownership, and operational responsibility.
- Build safe integration patterns for CI/CD pipelines so secrets are injected securely without appearing in logs, scripts, repositories, or build artefacts.
- Connect key rotation and secret rotation to service continuity, application configuration, and incident response requirements.
- Recognize when security controls should be enforced through architecture, automation, policy, monitoring, or operational process.
- Use this section to prepare for scenarios where security design must protect workloads without blocking legitimate cloud operations.
Implementing and Operating Databases in OCI
Develop the judgement needed to select, deploy, scale, monitor, and protect OCI database services. The focus includes Autonomous Database, Base Database services, performance, availability, cache usage, troubleshooting, and recovery planning.
- Evaluate database options such as Autonomous Database and Base Database services based on operational model, performance, control, and governance needs.
- Select architecture patterns that support database availability, backup, scalability, security, and integration with application tiers.
- Interpret performance and capacity planning requirements by considering workload behaviour, connection patterns, storage, compute, and growth expectations.
- Use OCI Cache where application performance, latency reduction, and scalable read patterns make caching more appropriate than database-only scaling.
- Design database monitoring approaches that surface actionable telemetry for availability, performance, capacity, backups, and operational incidents.
- Connect database backup and recovery choices to the wider disaster recovery strategy rather than treating them as separate administration tasks.
- Troubleshoot database and application performance problems by considering network paths, service limits, query behaviour, and dependency health.
- Apply security thinking to database access, encryption, secrets, private networking, auditability, and administrative privilege.
- Understand the tradeoff between managed convenience and control when choosing database deployment models.
- Use this section to prepare for questions that require matching database architecture to business-critical workload requirements.
Multi-Cloud and Hybrid Architecture Design
Prepare for advanced architecture scenarios involving OCI, Azure, Google Cloud, Oracle Database@Azure, Oracle Database@Google Cloud, Oracle Interconnect, Oracle Cloud VMware Solution, identity alignment, routing, segmentation, and governance.
- Evaluate multi-cloud solution architectures by considering business drivers, risk, data gravity, latency, operational governance, and service ownership.
- Understand Oracle Interconnect patterns for Azure and the architectural role of Oracle Database@Azure in enterprise database modernization.
- Understand Oracle Interconnect patterns for Google Cloud and the architectural role of Oracle Database@Google Cloud in cross-cloud deployments.
- Design hybrid cloud solutions using Oracle Cloud VMware Solution where VMware continuity, migration strategy, and operational familiarity are important.
- Align identity models across environments using federation awareness, role mapping, administrative boundaries, and governance controls.
- Plan routing, segmentation, inspection, and private connectivity models across OCI, on-premises networks, and other cloud platforms.
- Consider cross-cloud observability, incident response, access control, backup, disaster recovery, and data movement requirements.
- Identify when multi-cloud adds business value and when it introduces avoidable complexity, cost, latency, or operational risk.
- Connect database placement decisions to application latency, regulatory requirements, integration paths, and operational ownership.
- Use this section to prepare for exam scenarios where the best architecture spans more than one cloud or an existing data centre.
Workload and Data Migration to OCI
Build a professional migration mindset for OCI by planning workload movement, database migration, cutover, rollback, validation, downtime reduction, post-migration hardening, performance verification, and right-sizing.
- Design workload migration plans using Oracle Cloud Migrations with attention to discovery, dependency mapping, wave planning, and execution risk.
- Define cutover procedures, rollback plans, validation steps, stakeholder communication, and maintenance windows before migration begins.
- Implement and troubleshoot database and data migrations by focusing on data integrity, connectivity, downtime limits, and application dependency readiness.
- Minimize downtime through rehearsal, replication planning, sequencing, pre-checks, post-checks, and clear acceptance criteria.
- Preserve data integrity by validating source and target consistency, application behaviour, permissions, and operational monitoring after cutover.
- Harden workloads after migration by reviewing principals, secrets, firewall exposure, public endpoints, encryption, logging, and least privilege.
- Verify performance after migration through baseline comparison, right-sizing, capacity checks, cost review, and workload-specific tuning.
- Recognize when rehosting is suitable and when refactoring, replatforming, or redesign is needed to capture OCI benefits.
- Connect migration planning to landing zones, network design, identity, databases, disaster recovery, monitoring, and cost governance.
- Use this section to practise scenario decisions where migration success depends on operational planning as much as technical execution.
Observability, Operations, and Cost Optimization
Strengthen your ability to operate OCI environments after deployment. You will cover metrics, logs, events, alarms, actionable signal chains, incident response, SLO thinking, governance, tagging, budget controls, and cost optimization.
- Design observability models using metrics, logs, events, and alarms that produce actionable signals rather than excessive operational noise.
- Create alert routing and escalation principles that support timely response, ownership clarity, and reduced alert fatigue.
- Use telemetry correlation across compute, network, database, application, security, and platform layers during incident investigation.
- Apply SLA and SLO-style thinking to define availability, performance, recovery, and user-experience targets.
- Enforce governance and cost optimization strategies through tagging, budget monitoring, right-sizing, usage review, and approved architecture patterns.
- Use tag enforcement and budget visibility so ownership, chargeback, environment tracking, and cost accountability remain reliable.
- Connect operational excellence to runbooks, dashboards, capacity planning, change control, and continuous improvement after incidents.
- Recognize waste patterns such as oversized resources, idle environments, uncontrolled data transfer, poor storage choices, and ungoverned scaling.
- Understand how monitoring, security, availability, and cost decisions interact in long-running enterprise environments.
- Use this section to prepare for exam scenarios where design choices must remain supportable, measurable, and cost-aware after go-live.
Use the 10-section pathway to break professional OCI architecture into manageable domains while still seeing how landing zones, networking, security, availability, databases, migration, operations, and cost control connect across the platform.
Choose a 1Z0-997-25 Practice Section
Open any section directly and start focused practice on the OCI domain you want to strengthen. Topic-based revision helps you connect OCI services, improve architecture judgement, and build confidence with professional-level scenarios.
Each section opens in a new tab so you can keep the exam outline available while working through targeted OCI Architect Professional practice.
Build Professional OCI Architecture Readiness with a Clear Study Path
Use this preparation pathway to move beyond topic memorization and practise the reasoning expected of a professional OCI architect. Each section helps you connect services, constraints, risks, and operational choices before moving into focused practice.
The content is separated into recognizable professional domains so you can quickly decide whether to review landing zones, cloud-native design, enterprise networking, availability, disaster recovery, security, databases, migration, multi-cloud design, or operational governance.
This helps you revise professional OCI concepts without losing sight of the relationships between design choices, security controls, recovery objectives, service dependencies, and cost governance.
How this preparation path supports you
Have questions?
Frequently Asked Questions
These short answers help you plan your 1Z0-997-25 revision and make better use of the practice sections.
What is the purpose of this 1Z0-997-25 preparation pathway?
Use this page as a structured overview of the major Oracle Cloud Infrastructure Architect Professional areas before moving into section-based practice. It breaks enterprise OCI architecture into clearer, more manageable domains for revision.
How should I use the 10 sections on this page?
Start with one section at a time, complete the practice for that section, review the explanations, and then move to the next area. After covering all sections, return to weaker domains for targeted revision.
Do the practice links open in a new tab?
Yes. Each section is set to open in a new tab so you can move easily between revision notes, topic overview, and focused practice.
Is this page useful if I already have OCI Associate-level knowledge?
Yes. It is designed for professional-level revision, so it helps you move beyond basic service awareness into enterprise architecture decisions involving governance, security, availability, migration, multi-cloud integration, and operations.