Knowledge + Practice

CCNA Databases Questions

41 questions · Databases · All types, answers revealed

Practice these questions Domain overview All questions

1

MCQeasy

What is the primary architectural advantage of using Exadata Database Service on Dedicated Infrastructure compared to Exadata Database Service on Cloud@Customer?

A.It requires the customer to manage physical rack power, cooling, and hardware replacement

B.It exclusively supports non-relational database formats unlike Cloud@Customer

C.It eliminates the need for Virtual Cloud Networks (VCNs)

D.The physical Exadata hardware resides and operates entirely within an OCI data center managed by Oracle

AnswerD

Dedicated Infrastructure runs the Exadata hardware inside an Oracle-managed OCI data centre, so Oracle owns the physical environment. Cloud@Customer instead places that same hardware in the customer's own data centre, which is the architectural axis the question contrasts.

Why this answer

Exadata Database Service on Dedicated Infrastructure runs the Exadata hardware inside an OCI data center fully managed by Oracle, so the customer does not own or operate the physical infrastructure. This is the primary architectural advantage over Cloud@Customer, where the Exadata rack sits in the customer's own data center and the customer is responsible for power, cooling, and physical security.

Exam trap

1Z0-997-26 often tests the inversion of responsibility between Dedicated Infrastructure and Cloud@Customer — candidates must remember that Dedicated Infrastructure is Oracle-managed in OCI, while Cloud@Customer puts the hardware in the customer's data center with customer-managed facilities.

How to eliminate wrong answers

Option A is wrong because managing physical rack power, cooling, and hardware replacement is a characteristic of Cloud@Customer, not Dedicated Infrastructure — it is the opposite of the advantage. Option B is wrong because both offerings support Oracle relational databases (and Exadata is specifically optimized for them); neither is non-relational-only. Option C is wrong because both offerings still use VCNs for network isolation — Dedicated Infrastructure does not eliminate VCN requirements.

Practice this question →

2

MCQhard

An organization running an Oracle Exadata Database Service requires compliance auditing where all database administrative actions and sensitive data queries must be logged, tamper-proof, and retained in an isolated repository. Which combination of OCI and Oracle Database features provides this capability?

A.OCI Object Storage unversioned buckets with public read permissions

B.Oracle Data Safe combined with Database Unified Audit policies

C.Oracle Data Pump export logs stored in local temporary directories

D.Standard Linux syslog daemon writing to local disk partitions

AnswerB

Database Unified Audit policies capture administrative actions and sensitive queries, while Oracle Data Safe centralises and stores those audit records in a tamper-proof, isolated repository with retention controls. Together they satisfy the compliance auditing mandate for Exadata Database Service.

Why this answer

Oracle Data Safe combined with Database Unified Audit policies provides centralized, tamper-proof auditing for administrative actions and sensitive data queries. Data Safe collects audit trails into a secure repository, applies masking and security assessments, and Unified Auditing captures the required events at the database level.

Exam trap

The trap is choosing storage or OS-level logging (Object Storage, syslog, Data Pump logs) for compliance auditing — only Data Safe with Unified Auditing provides tamper-proof, centralized, database-aware audit trails.

How to eliminate wrong answers

Option A is wrong because unversioned buckets with public read permissions are insecure and do not provide tamper-proof audit logging — public access violates compliance. Option C is wrong because Data Pump export logs stored in local temporary directories are not tamper-proof, not centralized, and not an auditing mechanism. Option D is wrong because syslog to local disk is not tamper-proof, not isolated, and does not capture database-level administrative actions or sensitive queries.

Practice this question →

3

MCQmedium

You are configuring an Autonomous Database instance and need to restrict incoming database traffic so that only specific corporate subnet CIDR blocks can access the database service endpoints. Which feature should you configure?

A.OCI Web Application Firewall (WAF) attached directly to the database listener port

B.OCI Identity and Access Management dynamic groups

C.Database Vault realm restrictions

D.Autonomous Database Access Control Lists (ACLs) specifying allowed IP CIDR blocks

AnswerD

Autonomous Database ACLs restrict access at the database service endpoint level by permitting only specified IP CIDR blocks. This directly enforces the corporate subnet restriction, unlike VCN security lists or NSGs, which filter traffic at the network layer rather than the database endpoint itself.

Why this answer

Autonomous Database supports Access Control Lists (ACLs) that specify allowed IP CIDR blocks for database service endpoints. This is the native, supported mechanism to restrict incoming traffic to specific corporate subnets without deploying additional network appliances.

Exam trap

1Z0-997-26 often tests the misconception that WAF or IAM can restrict database network access — candidates must recognize that ADB ACLs are the correct CIDR-based control for database endpoints.

How to eliminate wrong answers

Option A is wrong because OCI WAF is designed for HTTP/HTTPS application traffic, not for database listener ports (e.g., TCPS 1522) — WAF cannot inspect or filter database protocol traffic. Option B is wrong because IAM dynamic groups control OCI resource principals' permissions, not network-level access to database endpoints. Option C is wrong because Database Vault realm restrictions control privileged user access and separation of duties within the database, not network CIDR-based access control.

Practice this question →

4

Multi-Selecthard

You are designing a cross-region disaster recovery strategy for an Oracle Exadata Database Service on Dedicated Infrastructure deployment. Which TWO steps or configurations are required to establish an Active Data Guard standby database in a remote OCI region?

Select 2 answers

A.Mount a shared block storage volume across both OCI regions using Network File System (NFS).

B.Enable automatic backups on the standby database using the same retention period as the primary.

C.Configure Standby Redo Logs (SRLs) on both the primary and standby databases sized identically to the online redo logs.

D.Configure Oracle GoldenGate bidirectional replication as the underlying transport mechanism.

E.Establish network connectivity between the primary and standby VCNs using a Dynamic Routing Gateway (DRG) and local or remote VCN peering.

AnswersC, E

Standby redo logs on both databases, sized identically to the online redo logs, let the standby receive and apply redo shipped from the primary. Active Data Guard requires this configuration to sustain real-time synchronisation across the remote region.

Why this answer

Option C is correct because Oracle Data Guard requires standby redo logs (SRLs) on both the primary and standby databases to receive redo from the primary and to support role transitions; best practice is to size them identically to the online redo logs and add one extra SRL group per thread. Option E is correct because an Active Data Guard standby in a remote OCI region needs network connectivity between the primary and standby VCNs, which in OCI is achieved with a Dynamic Routing Gateway (DRG) plus local or remote VCN peering (or equivalent DRG-based routing). Option A is not required because Data Guard transports redo over Oracle Net (TCP), not by mounting shared NFS block storage across regions, which is neither supported nor how Data Guard works.

Option B is not required because automatic backups on the standby are optional and independent of establishing the standby; Data Guard configuration does not depend on matching backup retention. Option D is not required because GoldenGate is a logical replication product, whereas Active Data Guard uses redo transport and apply, not GoldenGate, as its transport mechanism.

Exam trap

1Z0-997-26 often tests the misconception that shared storage or GoldenGate is required for Data Guard, when in fact Data Guard uses redo transport over the network and requires SRLs and proper VCN connectivity via DRG.

Practice this question →

5

MCQmedium

You are configuring disaster recovery for an Oracle Base Database system using Oracle Data Guard with Data Guard Broker. You need to perform a role transition where the primary database becomes the standby and the standby becomes the primary with zero data loss. Which Data Guard Broker command should you execute?

A.ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

B.CONVERT DATABASE TO PHYSICAL STANDBY;

C.SWITCHOVER TO <standby_database_name>;

D.FAILOVER TO <standby_database_name>;

AnswerC

SWITCHOVER performs a planned, reversible role transition with zero data loss, since the primary flushes all redo to the standby before roles reverse. This satisfies the stem's zero-data-loss requirement, unlike FAILOVER, which is for unplanned outages and may discard unapplied redo.

Why this answer

In Data Guard Broker, a switchover is a planned role transition where the primary becomes the standby and the standby becomes the primary with zero data loss. The command to perform a switchover is 'SWITCHOVER TO <standby_database_name>;' executed via DGMGRL. This ensures no data loss because the primary is synchronized with the standby before the transition.

Exam trap

The trap is confusing switchover with failover; candidates may select 'FAILOVER' thinking it is the command for role transition, but failover is for unplanned outages and may lose data, while switchover is planned and zero-data-loss.

How to eliminate wrong answers

Option A is wrong because 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;' is a SQL command to stop managed recovery on a standby, not a Data Guard Broker command for role transition. Option B is wrong because 'CONVERT DATABASE TO PHYSICAL STANDBY;' is not a valid Data Guard Broker command; conversion to standby is done via RMAN or SQL, not Broker. Option D is wrong because 'FAILOVER TO <standby_database_name>;' is used for a failover, which is an unplanned transition that may result in data loss, not a zero-data-loss switchover.

Practice this question →

6

MCQmedium

A retail company uses Oracle Autonomous Transaction Processing (ATP) with auto-scaling enabled. During a flash sale, the application observes that performance degrades despite auto-scaling being active. The architect reviews the ATP configuration and finds the base OCPU count is set to 4 with auto-scaling enabled. What is the most likely explanation for the degraded performance?

A.Auto-scaling requires the database to be restarted to take effect, so the extra OCPUs are not available until the next maintenance window.

B.Auto-scaling is disabled automatically when the database exceeds 80 percent CPU utilization for more than 15 minutes to protect the underlying infrastructure.

C.Auto-scaling on ATP only adjusts storage IOPS and does not change the number of OCPUs allocated to the database.

D.Auto-scaling triples the base OCPU count to a maximum of 12 OCPUs, but if the workload requires more than that or hits session or concurrency limits, performance still degrades.

AnswerD

With a base of 4 OCPUs, ATP auto-scaling can scale up to 3x, or 12 OCPUs, during peak demand. If the flash sale drives demand beyond 12 OCPUs' worth of work or hits other limits such as maximum sessions or parallel execution servers, throughput still suffers. The architect should raise the base OCPU count to lift the auto-scaling ceiling.

Why this answer

ATP auto-scaling can expand the base OCPU count by up to three times during demand spikes. A base of 4 OCPUs therefore tops out at 12 OCPUs, and a flash sale that needs more compute or hits session and concurrency limits will still see degraded performance. Raising the base OCPU count increases the auto-scaling ceiling and is the appropriate architectural response.

Exam trap

The trap here is believing that auto-scaling provides unlimited elasticity or that it only affects storage, when in fact it triples the base OCPU count within a fixed ceiling.

Practice this question →

7

MCQeasy

A startup wants to move an on-premises Oracle Database to OCI with minimal administration and no need to manage the underlying operating system or perform manual patching. The workload is a mixed OLTP and reporting application with unpredictable demand. Which OCI database service best fits these requirements?

A.Oracle Base Database Service on a virtual machine DB system, because it provides full OS access for tuning.

B.Oracle Database software on a bare metal compute instance, because the startup can install and configure the database exactly as needed.

C.Oracle Autonomous Database, because it automates patching, tuning, and scaling and requires no OS or infrastructure administration.

D.Oracle Exadata Database Service on Dedicated Infrastructure, because dedicated hardware guarantees the lowest latency for mixed workloads.

AnswerC

Autonomous Database automates patching, backups, tuning, and scaling, and the customer does not manage the operating system or infrastructure. For a startup with limited DBA resources and a mixed OLTP and reporting workload with unpredictable demand, the Autonomous Transaction Processing workload type with auto-scaling fits well, eliminating routine administration while handling variable load.

Why this answer

Autonomous Database is the only option that removes OS and infrastructure administration while automating patching, tuning, backups, and scaling. It suits a startup with limited DBA resources and a mixed, unpredictable workload because auto-scaling and autonomous tuning absorb demand variation. The other services either require substantial administration or provide dedicated infrastructure that exceeds the startup's operational capacity.

Exam trap

The trap here is equating high performance or dedicated hardware with the best fit, when the stated priority is minimal administration and no OS management.

Practice this question →

8

Multi-Selecthard

When designing a multi-database architecture with Oracle GoldenGate for high availability and load distribution, which THREE architectural considerations are critical for success? (Choose three.)

Select 3 answers

A.Routing all write transactions through a single read-only replica without replication

B.Implementing Conflict Detection and Resolution (CDR) rules for active-active multi-master topologies

C.Configuring unique primary key generation strategies (e.g., sequence offsets) to prevent key collisions

D.Managing DDL replication synchronization to ensure schema modifications match across nodes

E.Disabling all checkpointing to maximize real-time packet loss tolerance

AnswersB, C, D

Active-active multi-master topologies let the same row be updated at multiple nodes simultaneously, so CDR rules detect and resolve those conflicting changes. Without them, replication applies divergent updates and data diverges, breaking the load-distribution design.

Why this answer

Option B is correct because in an active-active multi-master GoldenGate topology, the same rows can be modified on multiple nodes simultaneously, so Conflict Detection and Resolution (CDR) rules are essential to deterministically resolve update/delete conflicts and prevent data divergence. Option C is correct because each node must generate non-overlapping keys; using unique sequence offsets (or ranges) per node prevents primary key collisions when inserts from different replicas are applied to the same table. Option D is correct because DDL changes must be captured and replicated in a coordinated way (e.g., via DDL replication and synchronized apply order) so that table structures, columns, and indexes remain identical across nodes, avoiding extract/replicat failures and metadata mismatches.

Option A is wrong because routing all writes to a single read-only replica without replication is not a GoldenGate HA/load-distribution design and would not propagate changes. Option E is wrong because disabling checkpointing removes recovery positioning, causing data loss and preventing reliable restart after failures.

Exam trap

The trap is treating GoldenGate multi-master as simple bidirectional replication — candidates overlook that without CDR, unique key strategies, and DDL sync, active-active topologies quickly suffer key collisions and data divergence.

Practice this question →

9

MCQmedium

You are designing a high availability disaster recovery architecture for an Oracle Base Database Service system deployed on a 2-node Virtual Machine DB System. You need to configure automated backups. Which storage destination is automatically used by OCI to store these automated backups?

A.A separate standby Oracle ASM disk group on Block Volume storage.

B.Local NVMe scratch disk attached to the primary database node.

C.OCI Object Storage bucket managed by the database service.

D.An independent File Storage Service (FSS) mount target shared across availability domains.

AnswerC

Automated backups on a Virtual Machine DB System are written to an OCI Object Storage bucket provisioned and managed by the database service itself, requiring no customer configuration. This satisfies the stem's constraint of an automatically used destination, since the service handles bucket creation, retention and lifecycle without manual intervention.

Why this answer

OCI Base Database Service automatically stores automated backups in an OCI Object Storage bucket that is managed by the database service itself, not visible or configurable as a customer bucket. This provides durable, cross-fault-domain storage without requiring the customer to provision or manage the bucket.

Exam trap

The trap is assuming the customer must provision or manage the Object Storage bucket for automated backups — OCI manages it transparently, and candidates often confuse it with manual Data Pump exports to a customer bucket.

How to eliminate wrong answers

Option A is wrong because a standby ASM disk group on Block Volume is used for Data Guard or local redundancy, not for automated backup storage. Option B is wrong because local NVMe scratch disks are ephemeral and not used for persistent backups — they are used for temporary storage or swap. Option D is wrong because FSS is a shared file system service that is not the automatic destination for Base Database Service automated backups; it can be used for manual exports or Data Pump but not the built-in automated backup target.

Practice this question →

10

Multi-Selecthard

You are optimizing the cost and performance of an Exadata Database Service on Dedicated Infrastructure environment hosting multiple large databases. Which THREE practices should you implement to achieve optimal resource utilization and cost efficiency?

Select 3 answers

A.Consolidate multiple non-CDB databases into a single Multitenant Container Database (CDB) with multiple PDBs.

B.Configure Exadata Smart Flash Cache policies appropriately for OLTP versus DSS workloads.

C.Migrate all table data to standard Block Volume storage to bypass Exadata storage servers.

D.Disable automatic backups entirely to save OCI Object Storage costs.

E.Dynamically scale OCPU counts on the Exadata infrastructure based on peak and off-peak workload schedules.

AnswersA, B, E

Consolidating non-CDBs into a single Multitenant CDB with multiple PDBs directly addresses the resource-utilisation constraint: PDBs share one instance's SGA, background processes and CPU, eliminating per-database overhead. This raises consolidation density on the same Exadata infrastructure, so fewer dedicated resources are provisioned, lowering cost while maintaining performance isolation.

Why this answer

Option A is correct because consolidating non-CDB databases into a single Multitenant Container Database with multiple PDBs improves consolidation density, reduces per-database overhead, and enables efficient resource sharing through PDB-level resource management on Exadata. Option B is correct because Exadata Smart Flash Cache policies (for example, keeping OLTP data cached while marking DSS scans as non-cacheable) ensure flash is used for latency-sensitive random I/O and not polluted by large sequential scans, improving performance and deferring costly capacity upgrades. Option E is correct because Exadata Database Service on Dedicated Infrastructure supports dynamic OCPU scaling, so matching OCPU counts to peak and off-peak schedules avoids paying for idle compute while preserving performance during demand peaks.

Option C is incorrect because moving table data to standard Block Volume bypasses Exadata storage servers, eliminating Smart Scan, storage indexes, and Exadata flash benefits, which hurts performance and cost efficiency. Option D is incorrect because disabling automatic backups removes data protection and is not a valid cost-optimization practice; backup costs should be managed through retention and tiering policies instead.

Exam trap

The trap is choosing options that seem cost-saving (like disabling backups or moving to Block Volume) but actually harm performance or risk data loss; the exam tests whether you understand Exadata's value proposition.

Practice this question →

11

Multi-Selecthard

Which THREE strategies are recommended when planning a large-scale database migration (exceeding 100 TB) from on-premises to Exadata Database Service on Dedicated Infrastructure with minimal downtime? (Choose three.)

Select 3 answers

A.Leveraging Transportable Tablespaces (TTS) combined with RMAN cross-platform conversion

B.Utilizing Oracle Zero Downtime Migration (ZDM) physical migration workflows

C.Copying database files across the public internet using standard FTP without encryption

D.Exporting the entire 100 TB database into a single plaintext SQL script using SQL*Developer

E.Configuring Oracle Data Guard or GoldenGate for ongoing delta synchronization prior to cutover

AnswersA, B, E

Transportable Tablespaces with RMAN cross-platform conversion moves datafiles at the physical level, transferring the bulk 100 TB quickly while only metadata is exported and imported. This minimises the cutover window, satisfying the minimal-downtime constraint for the large migration.

Why this answer

Option A is correct because Transportable Tablespaces (TTS) with RMAN cross-platform conversion moves datafiles at the physical level, avoiding the slow row-by-row logical extraction that would be impractical for 100 TB, and RMAN's CONVERT DATAFILE handles endianness/platform differences efficiently. Option B is correct because Oracle Zero Downtime Migration (ZDM) physical migration workflows are purpose-built for large on-premises-to-Exadata/ODA moves, orchestrating Data Guard-based synchronization and automated cutover to keep downtime minimal. Option E is correct because configuring Oracle Data Guard or Oracle GoldenGate for ongoing delta synchronization lets the bulk copy happen while changes continue to be applied, so only a brief final switchover is needed at cutover.

Option C is not recommended because unencrypted FTP over the public internet is insecure and unreliable for 100 TB of database files. Option D is not recommended because exporting 100 TB into a single plaintext SQL script via SQL Developer is a logical, serialized, and insecure approach that would take far too long and cannot meet minimal-downtime requirements.

Exam trap

The trap is choosing logical export/import or insecure file transfer for huge databases; the exam expects you to recognize that physical migration plus delta synchronization is the only realistic path to minimal downtime at 100 TB scale.

Practice this question →

12

MCQmedium

You are planning to migrate an Oracle Database to OCI using Zero Downtime Migration (ZDM). Which underlying Oracle migration technology does ZDM orchestrate behind the scenes for large databases requiring physical migration?

A.OCI Object Storage lifecycle policies exclusively

B.Oracle RMAN and Oracle Data Guard

C.Third-party ETL pipelines and CSV flat file generation

D.MySQL Enterprise Backup and InnoDB replication

AnswerB

ZDM orchestrates Oracle RMAN for the physical backup and restore of datafiles, then Oracle Data Guard to synchronise and cut over. This physical approach suits large databases where logical replication would be impractical, matching the stem's physical migration requirement.

Why this answer

Zero Downtime Migration (ZDM) orchestrates Oracle Recovery Manager (RMAN) for the initial physical backup and restore, and Oracle Data Guard for ongoing replication to minimize downtime during the migration to OCI. For large databases requiring physical migration, ZDM leverages these native Oracle technologies to ensure data consistency and near-zero downtime. RMAN handles the bulk data movement, while Data Guard keeps the target in sync until the cutover.

Exam trap

1Z0-997-26 often tests the underlying technologies ZDM uses, and candidates may incorrectly choose logical migration methods like ETL or confuse ZDM with third-party tools; the trap is not recognizing that ZDM is built on RMAN and Data Guard.

How to eliminate wrong answers

Option A is wrong because OCI Object Storage lifecycle policies are used for managing object storage tiers and retention, not for orchestrating database migration. Option C is wrong because third-party ETL pipelines and CSV flat files are logical migration methods, not the physical migration technology ZDM uses for large databases; they are slower and not zero-downtime. Option D is wrong because MySQL Enterprise Backup and InnoDB replication are for MySQL databases, not Oracle Database, and ZDM is an Oracle-specific tool.

Practice this question →

13

MCQmedium

You are designing an automated backup strategy for an Exadata Database Service on Dedicated Infrastructure. You want to ensure that incremental backups are taken daily and full backups weekly, with long-term retention stored in OCI Object Storage. Where are these backup schedules configured?

A.In the OCI Console under the database system backup configuration settings or via API/CLI

B.By modifying the crontab configuration file as root on the dom0 hypervisor node

C.By editing the initialization parameter file (spfile) using SQL*Plus

D.Via Oracle Enterprise Manager Cloud Control deployed exclusively on-premises

AnswerA

Autonomous and Exadata backup schedules are defined in the OCI Console's database backup configuration or through API/CLI, letting you set daily incremental and weekly full retention to Object Storage. This satisfies the stem's scheduling and long-term retention constraints.

Why this answer

Backup schedules for Exadata Database Service on Dedicated Infrastructure are configured through the OCI Console under the database system's backup configuration, or via the OCI API/CLI. These settings define the retention period, backup window, and whether backups are stored in OCI Object Storage, and they control the automated incremental and full backup cadence.

Exam trap

1Z0-997-26 often tests whether candidates know that backup scheduling is an OCI control-plane function, not an OS-level cron or database parameter; the trap is selecting crontab or spfile edits.

How to eliminate wrong answers

Option B is wrong because modifying crontab on the dom0 hypervisor is not a supported or safe way to configure database backups; dom0 is the control domain and direct edits can break the managed service. Option C is wrong because spfile parameters control database instance behavior, not OCI-level backup scheduling or Object Storage retention. Option D is wrong because Enterprise Manager Cloud Control is not the configuration point for OCI Exadata backup schedules, and it is not deployed exclusively on-premises for this purpose.

Practice this question →

14

MCQhard

An architect manages an Autonomous Database on Dedicated Infrastructure (ADB-D) with an Autonomous Container Database (ACD) that hosts several Autonomous Databases. During a maintenance window, the operations team needs to patch the ACD. What happens to the Autonomous Databases running on that ACD during the patching operation?

A.The Autonomous Databases continue serving read-only queries from the ACD's read replicas while writes are queued and replayed after patching completes.

B.Each Autonomous Database on the ACD is patched independently and remains available, because ADB-D patches at the pluggable database level without touching the container.

C.The Autonomous Databases on the ACD become unavailable while the container is patched and restarted, unless a standby ACD is configured and a switchover is performed first.

D.The Autonomous Databases are automatically relocated to another ACD in the same compartment with sufficient capacity, so end users experience no downtime.

AnswerC

Patching an Autonomous Container Database requires restarting the container, which makes the Autonomous Databases hosted on it unavailable for the duration. To avoid this outage, you can configure a standby ACD with Data Guard and perform a switchover before patching, then patch the original container while the standby serves the workload, then switch back.

Why this answer

Patching an Autonomous Container Database restarts the container, so every Autonomous Database hosted on it experiences downtime unless a standby ACD is configured and a switchover moves the workload before patching. A standby ACD with Data Guard provides the continuity path. Independent per-PDB patching, automatic relocation, and automatic read-replica fallback are not features of ADB-D patching.

Exam trap

The trap here is assuming that individual Autonomous Databases are patched independently of their container or that the service automatically moves them elsewhere during a container patch.

Practice this question →

15

MCQeasy

Which Autonomous Database workload type is specifically optimized for running complex analytical queries, machine learning, and data warehousing workloads?

A.Autonomous Data Warehouse (ADW)

B.Autonomous JSON Database (AJD)

C.Autonomous Transaction Processing (ATP)

D.Autonomous Apex Application Development (APEX)

AnswerA

Autonomous Data Warehouse (ADW) uses columnar storage and automatic indexing to accelerate complex analytical queries, machine learning and data warehousing. This directly satisfies the stem's requirement for a workload type optimised for analytics, unlike transaction-processing or mixed workloads, which prioritise row-based access and concurrency instead.

Why this answer

Autonomous Data Warehouse (ADW) is the Autonomous Database workload type specifically tuned for analytical workloads: it uses columnar compression, automatic indexing for analytics, materialized view refresh, and parallel execution optimized for complex queries, machine learning, and data warehousing. ATP is tuned for high-concurrency transactional workloads, and AJD is optimized for JSON document workloads.

Exam trap

The trap is assuming all Autonomous Database types are interchangeable — candidates must remember that ADW is analytics/ML, ATP is OLTP, AJD is JSON, and APEX is low-code development, each with distinct optimization targets.

How to eliminate wrong answers

Option B is wrong because Autonomous JSON Database (AJD) is optimized for schema-less JSON document storage and querying (SODA), not for complex analytical SQL or data warehousing. Option C is wrong because Autonomous Transaction Processing (ATP) is tuned for OLTP with row-based access patterns, high concurrency, and short transactions — not for large analytical scans. Option D is wrong because Autonomous APEX Application Development is a low-code application development service, not a workload type optimized for analytics or machine learning.

Practice this question →

16

MCQeasy

Which OCI database service provides fully managed Oracle Database instances running on dedicated virtual machines with root access and granular control over operating system parameters?

A.Oracle Exadata Database Service on Dedicated Infrastructure

B.OCI NoSQL Database service

C.Oracle Autonomous Database Serverless

D.Oracle Base Database service

AnswerD

Oracle Base Database Service provisions dedicated virtual machines, granting root access and control over OS parameters — exactly the granular control the stem demands. Unlike Autonomous Database, which locks down the operating system, this service exposes the underlying host, satisfying the requirement for customisation at the OS level.

Why this answer

Oracle Base Database service (formerly Bare Metal and VM DB systems) provisions fully managed Oracle Database instances on dedicated VMs or bare metal where you get SSH root access and can tune OS kernel parameters, huge pages, and network settings. It is the OCI offering that sits between fully autonomous (no OS access) and self-managed (you run everything). This matches the requirement for root access and granular OS control.

Exam trap

1Z0-997-26 often tests whether candidates conflate 'fully managed' with 'no OS access' — the trap is picking Autonomous Database or Exadata when the question explicitly requires root access and OS parameter control.

How to eliminate wrong answers

Option A is wrong because Exadata Database Service on Dedicated Infrastructure is a highly engineered, appliance-based platform where Oracle manages the Exadata infrastructure and OS — customers do not get root access to the Exadata nodes. Option B is wrong because OCI NoSQL Database is a key-value/document store, not an Oracle Database instance. Option C is wrong because Autonomous Database Serverless is fully managed with no OS access at all — you cannot SSH or tune kernel parameters.

Practice this question →

17

MCQeasy

Which OCI tool should a cloud architect recommend for automating the lifecycle management, patching, and backing up of a fleet of Oracle Base Database systems across multiple compartments?

A.OCI Compute Instance Scheduler

B.Oracle Cloud Infrastructure GoldenGate deployment console

C.OCI Identity and Access Management (IAM) policies

D.OCI Database Management service

AnswerD

OCI Database Management provides fleet-level lifecycle, patching and backup automation across compartments for Base Database systems. It is the service scoped to that administrative task, unlike infrastructure or monitoring tools that do not orchestrate patching.

Why this answer

OCI Database Management service is purpose-built for fleet-level lifecycle operations on Base Database and Exadata systems: it provides patching, backup management, performance monitoring, and compliance reporting across compartments from a single console. It integrates with OCI IAM for compartment-scoped access and supports both autonomous and non-autonomous databases. This is the only option that directly addresses patching and backup automation for a fleet of Base Database systems.

Exam trap

1Z0-997-26 often tests whether candidates confuse replication tools (GoldenGate) or scheduling tools (Instance Scheduler) with the dedicated database fleet management service — the trap is picking a tool that does one adjacent thing but not lifecycle management.

How to eliminate wrong answers

Option A is wrong because Compute Instance Scheduler only starts/stops compute instances on a schedule — it has no database patching or backup capability. Option B is wrong because GoldenGate is a data replication and integration tool, not a lifecycle/patching/backup manager. Option C is wrong because IAM policies control authorization and access, not operational lifecycle tasks like patching or backups.

Practice this question →

18

MCQmedium

You are migrating an Oracle Database to an Exadata Database Service on Dedicated Infrastructure. You need to ensure that database backups are stored securely with zero public internet exposure. What is the recommended networking architecture for backup transmission?

A.Deploy an internet gateway with IPSec VPN tunnels terminating at the backup bucket

B.Configure a Service Gateway in your VCN to access OCI Object Storage privately

C.Expose a NAT Gateway with strict IP whitelisting

D.Attach a secondary public IP address to the database VM guest nodes

AnswerB

A Service Gateway lets resources in the VCN reach OCI Object Storage over the Oracle network fabric, never traversing the public internet. Backup traffic therefore stays private while still landing in Object Storage, satisfying the zero-public-exposure constraint.

Why this answer

A Service Gateway in the VCN provides a private path from the VCN to OCI Object Storage (and other Oracle services) without traversing the internet or requiring a NAT or internet gateway. Traffic to Object Storage stays on the Oracle backbone network, so backups from Exadata Database Service on Dedicated Infrastructure are transmitted with zero public internet exposure, satisfying the security requirement.

Exam trap

The trap is confusing NAT Gateway with Service Gateway — candidates often think NAT provides private access, but NAT still uses the public internet, whereas only a Service Gateway keeps Oracle service traffic entirely on the Oracle network.

How to eliminate wrong answers

Option A is wrong because an internet gateway exposes the VCN to the public internet, and terminating IPSec tunnels at a backup bucket is not a supported architecture — Object Storage buckets are not VPN endpoints. Option C is wrong because a NAT Gateway still routes traffic through the public internet (with source NAT), so it does not meet the 'zero public internet exposure' requirement even with IP whitelisting. Option D is wrong because attaching a secondary public IP to database VM guest nodes directly exposes the database hosts to the internet, which is a severe security violation and unnecessary for backup traffic.

Practice this question →

19

MCQmedium

You are designing a high-availability architecture for an Oracle Base Database system across two Availability Domains (ADs) within a single OCI region. Which multi-database HA pattern ensures automatic failover with minimal data loss?

A.Oracle Data Guard configured between primary and standby database instances across ADs

B.Periodic RMAN duplication scripts executed via cron jobs every hour

C.Active-Active Oracle RAC cluster spanning multiple Availability Domains over long-distance synchronous interconnects

D.Shared OCI Block Volumes mounted simultaneously by database nodes in different ADs

AnswerA

Data Guard ships redo from the primary to a standby in a second AD, applying changes continuously. This gives automatic failover with minimal data loss, satisfying the cross-AD HA requirement, whereas single-AD or non-replicating patterns cannot survive an AD outage.

Why this answer

Oracle Data Guard is Oracle's native disaster-recovery and HA solution that maintains a synchronized standby database in a different Availability Domain. With Data Guard in Maximum Availability or Maximum Performance mode using asynchronous or synchronous redo transport, failover can be automated via Fast-Start Failover (FSFO) with the Data Guard broker, achieving minimal data loss (zero with SYNC, near-zero with ASYNC) and automatic role transition. This is the standard multi-AD HA pattern for Oracle Base Database on OCI.

Exam trap

1Z0-997-26 often tests whether candidates confuse backup strategies (RMAN, snapshots) with HA/failover strategies (Data Guard, RAC), so the trap is selecting a backup-based option when the question explicitly asks for automatic failover with minimal data loss.

How to eliminate wrong answers

Option B is wrong because hourly RMAN duplication is a batch backup/restore approach with an RPO of up to one hour and no automatic failover — it is a backup strategy, not an HA pattern, and would require manual intervention to promote the copy. Option C is wrong because Oracle RAC across Availability Domains over long-distance synchronous interconnects is not supported — RAC requires low-latency (sub-millisecond) interconnect, and OCI ADs are physically separated by kilometers, making cross-AD RAC cache fusion impractical and unsupported for production. Option D is wrong because OCI Block Volumes are zonal resources that cannot be simultaneously mounted read-write by nodes in different ADs; multi-attach is limited to specific use cases within the same AD and requires a cluster-aware filesystem, so this is not a valid HA pattern.

Practice this question →

20

MCQhard

An enterprise is implementing a multi-database architecture utilizing Oracle GoldenGate microservices on OCI Compute instances to replicate data between an operational Exadata database and an analytical Autonomous Data Warehouse. Which network security construct must be configured to allow communication between the GoldenGate deployment and the Autonomous Database instance?

A.Configure VCN security lists or Network Security Groups (NSGs) allowing outbound TCP port 1522 and inbound mTLS traffic, and supply the ADB wallet

B.Expose an API Gateway with public IP routing directly to the database undo tablespace

C.Configure a Local Peering Gateway with remote VCN route tables pointing to port 22

D.Attach an Internet Gateway directly to the Autonomous Database private IP address

AnswerA

GoldenGate microservices connect to Autonomous Data Warehouse over the dedicated TCPS endpoint on port 1522, requiring egress rules plus the ADB wallet for mutual TLS authentication. Security lists or NSGs must permit that traffic, satisfying the connectivity constraint.

Why this answer

GoldenGate microservices on OCI Compute connect to Autonomous Database using the ADB wallet for mTLS authentication and the ADB's TCPS listener on port 1522. The VCN security lists or NSGs must allow outbound TCP 1522 from the GoldenGate host and inbound mTLS traffic to the ADB, and the wallet must be supplied to GoldenGate for the connection to succeed. This is the standard secure connectivity pattern for ADB.

Exam trap

The trap is misunderstanding ADB connectivity — candidates may pick options involving public IPs, SSH port 22, or API Gateways, missing that ADB requires mTLS with a wallet over TCPS port 1522 and does not expose a directly attachable public IP.

How to eliminate wrong answers

Option B is wrong because API Gateway is an HTTP API management service and cannot route directly to a database undo tablespace — undo tablespaces are internal storage structures, not network endpoints, and this option is technically nonsensical. Option C is wrong because a Local Peering Gateway connects two VCNs in the same region, and port 22 is SSH, not the ADB TCPS port; pointing route tables to port 22 does not enable GoldenGate-to-ADB communication. Option D is wrong because Autonomous Database does not have a public IP address you can attach an Internet Gateway to — ADB connectivity is via a private endpoint (or public endpoint with ACLs) using the wallet and TCPS, not direct IGW attachment.

Practice this question →

21

MCQhard

An enterprise application running on Exadata Database Service on Dedicated Infrastructure experiences severe I/O contention due to a noisy neighbor batch reporting job. Which Exadata storage feature should you configure to isolate and guarantee I/O resources for critical online transaction processing (OLTP) workloads?

A.Exadata I/O Resource Management (IORM) with database-level resource plans

B.OCI Block Volume performance tiers (Higher VPU settings)

C.Autonomous Database concurrency limits in the OCI console

D.OCI Compute Auto-scaling configurations on the domU guest VMs

AnswerA

Exadata IORM with database-level resource plans allocates I/O bandwidth and IOPS per database, directly satisfying the isolation constraint against the noisy neighbour batch job. Unlike inter-database plans, database-level plans govern consumer groups within a single database, letting you cap the reporting job's I/O and guarantee throughput for critical OLTP workloads.

Why this answer

Exadata I/O Resource Management (IORM) is the Exadata storage-layer feature that lets you define resource plans allocating I/O shares, limits, and flash cache quotas per database, consumer group, or category. Configuring a database-level IORM plan lets you cap the batch reporting job's I/O so the OLTP workload's critical I/O is guaranteed. This is the purpose-built Exadata mechanism for noisy-neighbor isolation.

Exam trap

The trap is confusing OCI-level storage/compute tuning (Block Volume VPUs, autoscaling) with Exadata's internal storage resource management — only IORM operates at the Exadata cell layer to isolate I/O between workloads.

How to eliminate wrong answers

Option B is wrong because OCI Block Volume performance tiers (VPUs) apply to block storage volumes, not to Exadata storage cells — Exadata uses its own cell disks and ASM, not OCI Block Volume. Option C is wrong because Autonomous Database concurrency limits are an ADB feature and do not apply to Exadata Database Service on Dedicated Infrastructure, which is a different service. Option D is wrong because OCI Compute Auto-scaling on domU guest VMs scales compute resources, not storage I/O prioritization, and does not address cell-level contention.

Practice this question →

22

Multi-Selecthard

Which THREE features are unique or heavily enhanced capabilities of Oracle Exadata Database Service on Dedicated Infrastructure compared to standard OCI Base Database systems? (Choose three.)

Select 3 answers

A.Native support for attaching external Microsoft Azure Blob Storage containers as ASM disk groups

B.Automatic index creation managed entirely by the local Linux kernel swap daemon

C.Exadata Storage Server Resource Management (IORM) for fine-grained I/O prioritization

D.Exadata Smart Flash Cache and Persistent Memory (PMEM) integration for ultra-low latency I/O

E.Exadata Smart Scan offloading database query processing to storage servers

AnswersC, D, E

Exadata Storage Servers run storage cells with IORM, prioritising I/O between databases and workloads directly at the storage tier. Standard OCI Base Database lacks this cell-level intelligence, so fine-grained I/O prioritisation satisfies the stem's "unique or heavily enhanced" constraint on dedicated infrastructure.

Why this answer

Option C is correct because Exadata Database Service on Dedicated Infrastructure includes Exadata's I/O Resource Management (IORM), which lets you define and enforce fine-grained I/O prioritization and limits across databases, consumer groups, and interconnects—capabilities not available in standard OCI Base Database systems. Option D is correct because Exadata systems uniquely combine Exadata Smart Flash Cache with Persistent Memory (PMEM) to accelerate I/O and reduce latency for critical database workloads, a hardware-level optimization absent from Base Database. Option E is correct because Exadata Smart Scan offloads query processing (filtering, column projection, and some aggregation) to the Exadata Storage Servers, dramatically reducing data transferred to the database nodes—this storage-offload architecture is a defining Exadata feature not present in Base Database.

Option A is incorrect because Exadata does not natively attach Azure Blob Storage containers as ASM disk groups; ASM disks are provided by Exadata storage cells or local/attached block storage, not Azure Blob. Option B is incorrect because automatic index creation is not performed by a Linux kernel swap daemon; index management is handled by the database (e.g., Automatic Indexing in Oracle Database), and the swap daemon has no role in index creation.

Exam trap

1Z0-997-26 often tests whether candidates can distinguish Exadata-engineered features (Smart Scan, IORM, Smart Flash Cache/PMEM) from generic OCI services, luring them toward plausible-sounding but non-existent integrations like Azure Blob as ASM storage.

Practice this question →

23

Multi-Selectmedium

When planning a migration of Oracle databases to Oracle Autonomous Database (Serverless), which THREE migration methods or tools are natively supported or recommended by Oracle?

Select 3 answers

A.Oracle SQL Developer migration workbench / Data Loading features.

B.Oracle Zero Downtime Migration (ZDM) service.

C.Directly attaching on-premises ASM disk groups via iSCSI to the Autonomous container.

D.Oracle Data Pump (import/export).

E.Direct physical RMAN full database restore to Autonomous storage.

AnswersA, B, D

SQL Developer's migration workbench and Data Loading wizard connect directly to Autonomous Database, moving schemas and flat files without intermediate staging. This satisfies the stem's requirement for a natively supported Oracle tool, since Oracle documents it for Serverless migrations.

Why this answer

Oracle SQL Developer's migration workbench and Data Loading features (A) are natively supported for migrating to Autonomous Database, providing wizards to convert schemas and load data via the Data Pump or SQL*Loader paths. Oracle Zero Downtime Migration (ZDM) (B) is Oracle's recommended service for moving on-premises or cloud databases to Autonomous Database with minimal downtime, using Data Guard or logical migration workflows. Oracle Data Pump (D) is the standard logical export/import utility supported for loading data into Autonomous Database, typically via Object Storage or a database link.

Options C and E are not supported: Autonomous Database is a managed service that does not expose ASM disk groups or permit attaching on-premises storage via iSCSI, and physical RMAN restores to Autonomous storage are not possible because customers have no OS or storage-level access.

Exam trap

The trap is assuming that physical migration methods like RMAN restore or ASM disk attachment are possible with Autonomous Database. Candidates may think that because it's Oracle, physical methods work, but Autonomous is fully managed and only supports logical migration.

Practice this question →

24

Multi-Selecteasy

Which TWO tools or interfaces can administrators use to manage Oracle Autonomous Database instances in OCI? (Choose two.)

Select 2 answers

A.Local floppy disk drive image uploads

B.Windows Remote Desktop Connection (RDP) to the Autonomous database hypervisor

C.Direct physical serial console cable attached to Exadata rack blades

D.OCI Command Line Interface (CLI) and REST APIs

E.Oracle Cloud Infrastructure (OCI) Console

AnswersD, E

The OCI CLI and REST APIs expose the full Autonomous Database control surface, including provisioning, scaling and lifecycle operations, so administrators can manage instances programmatically or from a terminal. This satisfies the stem's requirement for management interfaces, complementing the OCI Console rather than replacing it.

Why this answer

Option D is correct because Oracle Autonomous Database is a fully managed OCI service whose lifecycle and management operations (such as scaling, starting/stopping, cloning, and viewing details) are exposed through the OCI Command Line Interface and the OCI REST APIs, which administrators can script and automate. Option E is correct because the OCI Console provides the web-based graphical interface where administrators can create, monitor, and manage Autonomous Database instances without writing code. The other options do not belong: A (floppy disk image uploads) is an obsolete local media method with no role in OCI cloud management, B (RDP to the Autonomous database hypervisor) is impossible because Oracle manages the infrastructure and customers have no hypervisor access, and C (physical serial console cable to Exadata rack blades) is not a customer-accessible management path in a managed cloud service.

Exam trap

1Z0-997-26 often tests the misconception that customers can access the underlying infrastructure (e.g., via RDP or serial console) — candidates must remember that Autonomous Database is fully managed and only accessible via cloud interfaces.

Practice this question →

25

MCQeasy

What is the primary benefit of using OCI Autonomous Database Serverless compared to Provisioned (Dedicated) infrastructure regarding database administration?

A.Oracle fully automates all patching, tuning, scaling, and provisioning with zero infrastructure management required

B.Customers must manually configure Exadata cell software versions

C.Serverless databases do not support automated backups

D.Customers are required to manually apply quarterly database security patches

AnswerA

Autonomous Database Serverless removes customer-side administration entirely: Oracle automates patching, tuning, scaling and provisioning, so no infrastructure management is required. This directly satisfies the stem's comparison against Provisioned Dedicated, where customers retain more control over patching schedules, scaling and host-level administration.

Why this answer

Autonomous Database Serverless is fully managed by Oracle: provisioning, patching, upgrades, tuning, scaling, and backups are automated with no customer access to the underlying Exadata infrastructure. This contrasts with Provisioned/Dedicated, where the customer still controls Exadata infrastructure lifecycle tasks even though the database itself is autonomous. The primary administrative benefit is therefore the elimination of infrastructure management overhead.

Exam trap

The trap here is conflating 'autonomous' with 'still requires some manual DBA work' — candidates who have on-premises Oracle experience often assume patching or backups remain customer responsibilities, but Serverless removes both entirely.

How to eliminate wrong answers

Option B is wrong because customers never manually configure Exadata cell software on Serverless — Oracle owns the entire stack, including cell patching. Option C is wrong because Serverless Autonomous Database includes automated backups by default with configurable retention, so the claim that backups are unsupported is factually false. Option D is wrong because quarterly security patches are applied automatically by Oracle during maintenance windows, not manually by the customer.

Practice this question →

26

Multi-Selecteasy

Which TWO editions of Oracle Database are available when deploying an Oracle Base Database system on OCI? (Choose two.)

Select 2 answers

A.Oracle Database Micro Edition (ME)

B.Oracle Database Enterprise Edition (EE)

C.Oracle Database Web Edition (WE)

D.Oracle Database Standard Edition 2 (SE2)

E.Oracle Database Personal Edition (PE)

AnswersB, D

Oracle Base Database Service on OCI supports only Enterprise Edition and Standard Edition, so EE qualifies. Enterprise Edition provides the full feature set, including multitenant, Real Application Clusters and advanced security options, which the Base Database Service architecture requires for its high-availability and pluggable database deployments.

Why this answer

Oracle Base Database Service on OCI supports Oracle Database Enterprise Edition (EE), option B, which provides the full feature set including options like RAC, Data Guard, partitioning, and advanced security for mission-critical workloads. It also supports Oracle Database Standard Edition 2 (SE2), option D, a lower-cost edition suited for smaller deployments with up to two sockets per node. Options A, C, and E are not valid Oracle Database editions offered on OCI: Oracle Database Micro Edition (ME) and Web Edition (WE) are not real Oracle Database editions, and Personal Edition (PE) is a desktop-only edition not available for cloud deployment.

Exam trap

The trap is picking non-existent or desktop editions (ME, WE, PE) because they sound plausible — only EE and SE2 are valid for OCI Base Database Service.

Practice this question →

27

MCQeasy

Your development team needs to scale up CPU cores for an Autonomous JSON Database instance dynamically without restarting the application or causing downtime. Which feature should you use?

A.Auto-scaling with Oracle Data Guard switchover.

B.OCI Compute Instance resizing via instance pool configuration.

C.Manual cold restart of the container database.

D.Autonomous Database Elastic Resource Scaling.

AnswerD

Elastic Resource Scaling lets Autonomous Database add or remove CPU cores online, with no restart and no interruption to active sessions. This satisfies the stem's requirement for dynamic scaling without downtime, unlike manual scaling, which requires a brief period of inaccessibility.

Why this answer

Autonomous Database Elastic Resource Scaling allows you to scale CPU cores up or down dynamically without downtime, application restarts, or manual intervention. It is the native ADB feature for on-demand compute scaling and applies to Autonomous JSON Database as well. Because it is built into the service, the change takes effect while the database remains online.

Exam trap

The trap is conflating IaaS compute resizing (OCI Compute instance shapes) or Data Guard operations with Autonomous Database scaling, when the correct answer is the ADB-native Elastic Resource Scaling feature that works online without downtime.

How to eliminate wrong answers

Option A is wrong because Data Guard switchover is a disaster-recovery role transition, not a compute-scaling mechanism, and it has nothing to do with adding CPU cores. Option B is wrong because OCI Compute instance resizing applies to IaaS virtual machines, not to a managed Autonomous Database, which does not expose the underlying compute host for resizing. Option C is wrong because a manual cold restart of the container database would cause downtime — the exact opposite of the requirement — and is not how ADB scales compute.

Practice this question →

28

MCQhard

An organization is designing a disaster recovery strategy using Exadata Database Service on Dedicated Infrastructure. They require an Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of zero for an enterprise database handling mission-critical workloads. Which Data Guard configuration should be implemented?

A.Oracle Active Data Guard configured in Maximum Protection mode with synchronous transport

B.Manual RMAN backup replication via OCI Object Storage every 15 minutes

C.Oracle Data Guard configured in Maximum Performance mode with asynchronous transport

D.Oracle GoldenGate real-time replication with asynchronous extract configurations

AnswerA

Maximum Protection with synchronous transport guarantees zero data loss (RPO zero) because commits are acknowledged only after redo reaches the standby. Synchronous redo transport also enables fast failover, meeting the sub-30-second RTO required for mission-critical workloads.

Why this answer

RPO of zero requires synchronous redo transport so no committed transaction can be lost, and RTO under 30 seconds requires a standby that is already mounted, open read-only, and ready for immediate failover. Maximum Protection mode with Active Data Guard satisfies both: SYNC transport guarantees zero data loss, and Active Data Guard keeps the standby continuously applying redo so failover is near-instant. This is the only option that meets both objectives simultaneously.

Exam trap

1Z0-997-26 often tests the RPO/RTO mapping to Data Guard protection modes, and the classic mistake is choosing Maximum Performance because it sounds fast — but 'Performance' refers to primary throughput, not recovery speed, and it sacrifices zero-RPO.

How to eliminate wrong answers

Option B is wrong because 15-minute RMAN backup replication yields an RPO of up to 15 minutes and an RTO measured in hours for restore and recovery — nowhere near zero/30s. Option C is wrong because Maximum Performance mode uses asynchronous transport, which can lose the last few transactions on failover, violating the zero-RPO requirement. Option D is wrong because GoldenGate asynchronous extract introduces replication lag and does not guarantee zero data loss on unplanned failover, and it is not the Oracle-recommended DR mechanism for this RTO/RPO profile.

Practice this question →

29

MCQmedium

An architect is designing an Oracle Autonomous JSON Database instance to store flexible document workloads. Which feature is automatically enabled on Autonomous JSON Database that distinguishes it from general-purpose Autonomous Transaction Processing instances regarding storage management?

A.Automatic conversion of all JSON documents into relational third-normal-form tables upon ingestion

B.Mandatory requirement to define fixed database schemas via JSON Schema validators before inserting data

C.Storage and indexing are specifically optimized for JSON collections with restrictions on non-JSON relational tables

D.Exclusion of automated backups to reduce operational overhead

AnswerC

Autonomous JSON Database automatically applies JSON-centric storage and indexing optimisations to collections, and restricts non-JSON relational tables. This storage-management distinction separates it from general-purpose Autonomous Transaction Processing, which permits full relational schemas without that JSON-specific tuning.

Why this answer

Autonomous JSON Database is a specialized ADB workload type whose storage and indexing are optimized for JSON collections, and it restricts the use of non-JSON relational tables. This distinguishes it from general-purpose Autonomous Transaction Processing, which supports full relational schemas alongside JSON. The optimization targets document-style access patterns and JSON-native indexing.

Exam trap

The trap is assuming Autonomous JSON Database is just ATP with a JSON label, when in fact it has a distinct storage/indexing optimization and a restriction on non-JSON relational tables that candidates must recognize.

How to eliminate wrong answers

Option A is wrong because Autonomous JSON Database does not automatically convert all JSON documents into third-normal-form relational tables; it stores and indexes JSON natively using Oracle's JSON type and SODA APIs. Option B is wrong because JSON Schema validators are optional, not mandatory — one of the advantages of JSON is schema flexibility, and AJD does not force fixed schemas before inserts. Option D is wrong because automated backups are a standard ADB feature and are not excluded in Autonomous JSON Database; backups are still performed.

Practice this question →

30

MCQmedium

An enterprise application running on Oracle Autonomous Transaction Processing (ATP) requires dedicated infrastructure isolation for compliance reasons. You need to provision an Autonomous Database on Dedicated Exadata Infrastructure. Which architectural step is mandatory before you can provision the database instance?

A.Contact Oracle Support to manually allocate physical rack boundaries in your tenancy region.

B.Create an Autonomous Exadata Infrastructure resource in your compartment and virtual cloud network.

C.Create a Pluggable Database (PDB) manually via SQL*Plus on an existing multitenant container database.

D.Provision a standard Exadata Cloud Service cluster using the Database management service console.

AnswerB

Dedicated Autonomous Database requires an Autonomous Exadata Infrastructure resource, created in a compartment and associated with a virtual cloud network, as the underlying Exadata platform. Provisioning the database instance is impossible until that infrastructure resource exists.

Why this answer

Autonomous Database on Dedicated Exadata Infrastructure (ADB-D) requires a two-step provisioning model: first create the Autonomous Exadata Infrastructure (AEI) resource, which allocates the dedicated Exadata hardware in your compartment and VCN, then provision the Autonomous Container Database and finally the Autonomous Database on top of it. Without the AEI, there is no dedicated infrastructure to host the ADB, so this step is mandatory.

Exam trap

The trap is conflating Exadata Cloud Service (ExaCS) with Autonomous Database on Dedicated Infrastructure — candidates who pick option D miss that ADB-D has its own dedicated provisioning resource (AEI) and does not use the ExaCS console workflow.

How to eliminate wrong answers

Option A is wrong because Oracle does not require a support ticket to allocate rack boundaries — customers self-provision AEI through the OCI Console, CLI, or API within their own tenancy and region. Option C is wrong because manually creating a PDB via SQL*Plus is a manual multitenant operation on a traditional CDB, not part of the ADB-D provisioning workflow; ADB-D uses Autonomous Container Databases managed by Oracle. Option D is wrong because Exadata Cloud Service (ExaCS) is a different product from Autonomous Database on Dedicated Infrastructure — ExaCS gives you a full Exadata cluster with OS access, whereas ADB-D is fully managed and requires the AEI resource, not an ExaCS cluster.

Practice this question →

31

Multi-Selecthard

When designing a high-availability and disaster recovery architecture for an enterprise Oracle Database on OCI, which THREE components or patterns are crucial for achieving optimal recovery and uptime? (Choose three.)

Select 3 answers

A.Automated and policy-driven backups to OCI Object Storage with cross-region replication

B.Relying solely on local ephemeral NVMe drive snapshots for disaster recovery

C.Oracle Data Guard standby database in a remote region for disaster recovery

D.Stretching a single-node database VM across distinct cloud regions using unencrypted NFS mounts

E.Oracle Real Application Clusters (RAC) across fault domains or availability domains for local HA

AnswersA, C, E

Policy-driven backups replicated cross-region to OCI Object Storage give an independent recovery copy that survives regional loss, underpinning both uptime and disaster recovery. It satisfies the recovery objective by enabling restore when primary database copies are unavailable.

Why this answer

Option A is correct because automated, policy-driven backups written to OCI Object Storage and replicated across regions provide durable, off-site recovery points that survive regional failures and satisfy RPO/RTO objectives. Option C is correct because Oracle Data Guard maintains a synchronized standby database in a remote region, enabling fast failover and near-zero data loss for regional disaster recovery. Option E is correct because Oracle RAC spread across fault domains or availability domains provides local high availability by eliminating single points of failure and enabling instance-level failover within a region.

Option B is incorrect because local ephemeral NVMe snapshots are tied to the compute instance and are lost if the host or region fails, so they cannot serve as a disaster recovery mechanism. Option D is incorrect because a single-node database VM cannot be stretched across regions, and unencrypted NFS mounts introduce security and latency problems that undermine both availability and compliance.

Exam trap

The trap is selecting options that sound like HA/DR but rely on ephemeral or unsupported storage (local NVMe, unencrypted NFS across regions) — the exam tests whether you know the difference between durable, supported HA/DR patterns and anti-patterns.

Practice this question →

32

MCQeasy

You are provisioning an Autonomous Data Warehouse (ADW) instance and want to configure network access so that only specific corporate IP addresses can connect to the database. Which feature should you enable?

A.Autonomous Database Access Control Lists (ACLs).

B.Virtual Cloud Network (VCN) Security Lists only.

C.OCI Web Application Firewall (WAF) rule sets.

D.OCI Identity and Access Management (IAM) dynamic groups.

AnswerA

ACLs restrict connections to a defined list of allowed CIDR blocks or IP addresses at the network layer, so only the specified corporate ranges can reach the ADW instance. This directly satisfies the requirement to permit specific corporate IPs while blocking all other sources.

Why this answer

Autonomous Database Access Control Lists (ACLs) are the native ADB feature that restricts connections to a defined set of public IP addresses or CIDR blocks, or to a private endpoint. Enabling an ACL on the ADW instance ensures only the specified corporate IP ranges can reach the database listener, satisfying the requirement directly.

Exam trap

The trap is assuming VCN Security Lists apply to Autonomous Database — ADB is a managed service outside the customer VCN unless a private endpoint is configured, so subnet-level Security Lists do not govern its public listener.

How to eliminate wrong answers

Option B is wrong because VCN Security Lists control traffic at the subnet/VNIC layer for resources inside a VCN, but ADW is a managed service whose endpoint is not directly governed by customer Security Lists unless accessed via private endpoint. Option C is wrong because OCI WAF protects HTTP/HTTPS web applications, not the Oracle SQL*Net protocol used by ADW. Option D is wrong because IAM dynamic groups grant permissions to OCI resources for principals — they do not restrict which source IPs can connect to a database.

Practice this question →

33

MCQhard

You are configuring transparent data encryption (TDE) for an Oracle Database on Exadata Database Service using OCI Vault for master encryption key management. What happens if the database loses connectivity to the OCI Vault key management service?

A.The database instantly crashes and forces an immediate failover to the standby database

B.The database automatically falls back to self-managed wallet storage without alerting administrators

C.The database continues to run using keys cached in memory for a period, but cannot be restarted until connectivity to OCI Vault is restored

D.All encrypted data files are automatically wiped to prevent security breaches

AnswerC

OCI Vault connectivity loss does not halt a running database: the TDE master key remains cached in memory, so operations continue. However, restart requires re-fetching the key, so the instance cannot come back up until Vault is reachable again.

Why this answer

When TDE uses OCI Vault as the external key management service, the database caches the master encryption key in memory after first retrieval. If connectivity to OCI Vault is lost, running instances continue to operate using the cached key, but any restart or new instance mount fails because the key cannot be fetched to open the TDE wallet. This is the documented behavior for external key management with TDE.

Exam trap

1Z0-997-26 often tests the misconception that losing Vault connectivity immediately crashes the database; the trap is ignoring the in-memory key cache that keeps running instances alive.

How to eliminate wrong answers

Option A is wrong because the database does not instantly crash on Vault connectivity loss; it continues running with cached keys, and failover is not automatic. Option B is wrong because there is no silent fallback to a self-managed wallet; the database cannot switch key stores without reconfiguration, and administrators are alerted. Option D is wrong because encrypted data files are never wiped automatically; that would be catastrophic data loss and is not a TDE behavior.

Practice this question →

34

MCQmedium

Your development team wants to connect securely to an Autonomous Database (Serverless) instance using mutual TLS (mTLS) authentication. Where must the client application obtain the required credentials to establish this secure connection?

A.Download the database connection wallet zip file from the OCI Console or CLI and extract it on the client host

B.Generate a Kerberos ticket granting service token via the IAM security console

C.Retrieve the master encryption key directly from OCI Vault using an API key

D.Configure a public SSL certificate issued by Let's Encrypt in the database parameter settings

AnswerA

Mutual TLS requires the client to present the database's trusted certificates and private key. These reside in the connection wallet zip, downloadable from the OCI Console or CLI, which must be extracted on the client host so the application can reference its contents.

Why this answer

For mTLS connections to Autonomous Database Serverless, the client must download the connection wallet zip from the OCI Console or CLI (or via the ADB API) and extract it on the client host. The wallet contains the client credentials (e.g., cwallet.sso, tnsnames.ora, sqlnet.ora) required to authenticate the client to the database over TLS. Without the wallet, mTLS cannot be established.

Exam trap

1Z0-997-26 often tests whether candidates confuse the TDE master key in OCI Vault with the client connection wallet; the trap is selecting Vault as the source of mTLS credentials.

How to eliminate wrong answers

Option B is wrong because Kerberos is a separate authentication protocol not used for ADB mTLS; IAM does not issue Kerberos tickets for database connections. Option C is wrong because the master encryption key in OCI Vault is for TDE at-rest encryption, not for client TLS authentication, and exposing it to clients would be a severe security violation. Option D is wrong because ADB does not accept arbitrary public SSL certificates configured via database parameters; the wallet provides the Oracle-managed certificates and keys.

Practice this question →

35

MCQeasy

What is the primary purpose of OCI Database Actions (SQL Developer Web) when working with an Oracle Autonomous Database?

A.To configure physical Exadata storage cell disks and flash cache parameters

B.To monitor physical VCN packet drops and firewall logs

C.To manage OCI IAM user groups and federation settings across enterprise identity providers

D.To provide a web-based development and management interface for executing SQL, querying data, and managing database users

AnswerD

Database Actions provides a browser-based interface for running SQL, querying data, and managing users on Autonomous Database, removing the need for local client tools. This directly satisfies the requirement for a web-based development and management interface.

Why this answer

OCI Database Actions (SQL Developer Web) is a web-based tool that provides a development and management interface for Autonomous Database, allowing users to execute SQL, query data, manage database users, and perform other administrative tasks. It is the primary browser-based interface for interacting with Autonomous Database.

Exam trap

The trap is overestimating the scope of Database Actions, thinking it includes infrastructure or networking management. Candidates may confuse it with broader OCI management tools.

How to eliminate wrong answers

Option A is wrong because configuring physical Exadata storage cell disks and flash cache parameters is an infrastructure-level task performed by Oracle Cloud operations, not exposed to customers via Database Actions. Option B is wrong because monitoring VCN packet drops and firewall logs is a networking task handled by OCI Networking services, not Database Actions. Option C is wrong because managing IAM user groups and federation is an identity and access management function in OCI Console, not part of Database Actions.

Practice this question →

36

MCQeasy

When creating an Oracle Base Database system, which database edition options are available for licensing on OCI?

A.Oracle Database Express Edition (XE) exclusively

B.Standard Edition 2, Enterprise Edition, Enterprise Edition High Performance, and Enterprise Edition Extreme Performance

C.Microsoft SQL Server Enterprise Edition

D.MySQL Enterprise Edition and PostgreSQL Community Edition only

AnswerB

Oracle Base Database Service on OCI offers exactly these four editions: Standard Edition 2, Enterprise Edition, Enterprise Edition High Performance, and Enterprise Edition Extreme Performance. The two EE variants differ by included options such as RAC, Active Data Guard, and Database In-Memory, satisfying the stem's licensing constraint.

Why this answer

Oracle Base Database Service on OCI offers the same commercial editions as on-premises Oracle Database: Standard Edition 2, Enterprise Edition, Enterprise Edition High Performance, and Enterprise Edition Extreme Performance. These are the licensing options available when provisioning a Base Database system.

Exam trap

1Z0-997-26 often tests the misconception that XE or non-Oracle databases are available on Base Database, when the exam expects knowledge of the four commercial Oracle editions (SE2, EE, EE-HP, EE-EP).

How to eliminate wrong answers

Option A is wrong because Express Edition (XE) is a free, limited edition not offered as a licensing option for OCI Base Database systems. Option C is wrong because Microsoft SQL Server is a competitor product and is not available on Oracle Base Database. Option D is wrong because MySQL and PostgreSQL are separate database services on OCI, not editions of Oracle Base Database.

Practice this question →

37

MCQmedium

You need to migrate an on-premises Oracle Database to OCI Exadata Database Service using Oracle GoldenGate for zero-downtime migration with bi-directional replication. Which critical design consideration must be addressed regarding table design on both databases?

A.Primary keys must be omitted to allow duplicate row insertion across databases

B.Tables must have primary keys or unique identifiers, and Conflict Detection and Resolution (CDR) must be configured

C.Tables must not contain any indexes, triggers, or constraints

D.All tables must be converted to temporary unlogged tables

AnswerB

Bi-directional GoldenGate replication requires primary keys or unique identifiers so each row can be uniquely matched across sites; without them, updates and deletes cannot be applied deterministically. CDR then resolves conflicting changes from both directions, preventing data divergence.

Why this answer

For bi-directional replication with Oracle GoldenGate, tables must have primary keys or unique identifiers to ensure that each row can be uniquely identified for conflict detection and resolution. Conflict Detection and Resolution (CDR) must be configured to handle conflicts that arise when the same row is modified on both databases. This is critical for zero-downtime migration with bi-directional replication.

Exam trap

The trap is thinking that primary keys can be omitted for replication or that constraints must be removed; candidates may also overlook the need for CDR in bi-directional setups, leading to data conflicts.

How to eliminate wrong answers

Option A is wrong because omitting primary keys would prevent GoldenGate from uniquely identifying rows, leading to duplicate rows and data corruption; primary keys are essential for replication. Option C is wrong because tables can and often do contain indexes, triggers, and constraints; GoldenGate supports these, and they do not need to be removed. Option D is wrong because converting tables to temporary unlogged tables is not a requirement and would be inappropriate for a production migration; GoldenGate replicates standard tables.

Practice this question →

38

MCQhard

An architect is designing an Oracle Exadata Database Service on Dedicated Infrastructure deployment with multiple VM clusters on a single Exadata rack. Which architectural feature allows secure isolation of CPU, memory, and database workloads between these distinct VM clusters?

A.OCI Block Volume volume group replicas synchronized via block replication

B.Software-defined VLAN tagging enforced by the OCI Virtual Cloud Network (VCN) hypervisor only

C.Autonomous Database container database resource pools sharing a single OS kernel

D.Hard partitioning using Oracle VM (dom0/domU) hypervisor virtualization on the database servers

AnswerD

Oracle VM hard partitioning assigns dedicated CPU, memory, and I/O resources to each VM cluster through the dom0/domU hypervisor, providing strict isolation between workloads on the same Exadata rack. This prevents one cluster's activity from consuming another's resources, satisfying the secure isolation requirement.

Why this answer

Exadata Database Service on Dedicated Infrastructure uses Oracle VM (OVM) with dom0/domU architecture to provide hard partitioning between VM clusters. Each VM cluster runs in its own set of domU guests on the database servers, with CPU, memory, and I/O isolated by the hypervisor. This hard partitioning is what allows multiple VM clusters to coexist securely on a single Exadata rack.

Exam trap

1Z0-997-26 often tests whether candidates confuse network isolation (VLANs) or storage replication with compute isolation; the trap is picking a network or storage feature when the question asks about CPU and memory partitioning.

How to eliminate wrong answers

Option A is wrong because Block Volume volume group replicas are storage-level replication for data durability, not a mechanism for isolating CPU and memory between VM clusters. Option B is wrong because VLAN tagging is a network isolation feature, not CPU/memory isolation, and it does not partition compute resources. Option C is wrong because Autonomous Database resource pools share a single OS kernel within a container database, which is the opposite of hard partitioning and does not apply to Exadata VM clusters.

Practice this question →

39

MCQeasy

An enterprise requires deploying an Oracle Autonomous Database on Dedicated Infrastructure to meet stringent data isolation and security mandates. Which foundational resource must be provisioned first before creating the Autonomous Container Database?

A.An Autonomous Database on Shared Infrastructure instance

B.A standard Oracle Base Database system

C.A Virtual Cloud Network with a default database subnet only

D.An Autonomous Exadata Infrastructure resource

AnswerD

Autonomous Exadata Infrastructure provisions the dedicated Exadata hardware and networking that hosts the container database, delivering the physical isolation the security mandate demands. It is the prerequisite layer: no Autonomous Container Database can be created until this infrastructure exists in the tenancy.

Why this answer

To deploy an Autonomous Database on Dedicated Infrastructure, the foundational resource is the Autonomous Exadata Infrastructure (AEI). This is a dedicated Exadata system in OCI that provides the hardware and infrastructure for hosting Autonomous Container Databases (ACDs). The AEI must be provisioned first because it supplies the compute, storage, and network resources that the ACDs and subsequent Autonomous Databases will use.

Without an AEI, you cannot create an ACD or any dedicated autonomous databases.

Exam trap

1Z0-997-26 often tests the distinction between shared and dedicated infrastructure, and candidates may mistakenly think that a VCN or a Base Database system is the foundational resource, but the correct answer is the Autonomous Exadata Infrastructure.

How to eliminate wrong answers

Option A is wrong because an Autonomous Database on Shared Infrastructure is a completely different deployment model that does not provide the dedicated, isolated infrastructure required for dedicated autonomous databases. Option B is wrong because a standard Oracle Base Database system is a different service (Base Database Service) and is not used as the foundation for Autonomous Database on Dedicated Infrastructure. Option C is wrong because a Virtual Cloud Network with a default database subnet is a networking component that is necessary but not sufficient; it does not provide the dedicated Exadata infrastructure required.

The AEI is the specific foundational resource that must be provisioned first.

Practice this question →

40

MCQmedium

Your organization runs a multi-tenant Oracle Base Database Service and you need to monitor the storage utilization of individual Pluggable Databases (PDBs) within a Container Database (CDB). Which OCI native service and metric should you review?

A.OCI Logging Analytics with custom log parsers for alert.log.

B.OCI Database Management service PDB storage metrics.

C.Compute Instance metrics via OCI Monitoring service agent.

D.Autonomous Health Framework (AHF) health check reports.

AnswerB

Database Management surfaces PDB-level storage metrics, including allocated and used space per pluggable database, rather than only CDB-wide figures. This granularity is what the multi-tenant scenario demands, since container-level metrics cannot isolate which PDB is consuming storage.

Why this answer

The OCI Database Management service provides native monitoring for Oracle databases, including PDB-level storage metrics. It collects and displays metrics such as tablespace usage, datafile size, and storage utilization for each PDB within a CDB. This is the correct OCI-native service for monitoring individual PDB storage.

Exam trap

1Z0-997-26 often tests the assumption that host-level monitoring or log analytics can provide PDB storage metrics — candidates must remember that OCI Database Management is the native service for database-level metrics.

How to eliminate wrong answers

Option A is wrong because OCI Logging Analytics with custom log parsers for alert.log is a log analysis tool, not a metrics service for PDB storage utilization; it would require custom parsing and does not provide native storage metrics. Option C is wrong because Compute Instance metrics via the OCI Monitoring service agent report host-level metrics (CPU, memory, disk I/O) but not PDB-level storage metrics inside the database. Option D is wrong because the Autonomous Health Framework (AHF) health check reports are diagnostic tools for Oracle databases, not a continuous monitoring service for PDB storage metrics in OCI.

Practice this question →

41

MCQhard

An enterprise application uses an Oracle Autonomous Transaction Processing database and encounters intermittent application-level timeouts during peak concurrency spikes. Upon investigating, you notice that queued statements are waiting due to resource limits. Which Autonomous Database feature should you adjust to manage concurrency and statement queuing behavior?

A.The physical memory size of the OCI Compute host instance running the application

B.Linux kernel swappiness parameters on the database host

C.OCI Virtual Cloud Network security list packet drop thresholds

D.Consumer groups and resource management rules via DBMS_RESOURCE_MANAGER or resource profile settings

AnswerD

Consumer groups with DBMS_RESOURCE_MANAGER map sessions to resource profiles, letting you cap parallelism and set queuing thresholds per workload. This directly governs how statements wait when concurrency spikes exhaust resources, satisfying the requirement to manage statement queuing behaviour rather than merely scaling compute.

Why this answer

Autonomous Database uses Database Resource Manager (DBRM) consumer groups and resource plans to control how sessions share CPU, parallelism, and queued statements. When concurrency spikes cause statements to queue, the fix is to define or adjust consumer groups and resource management rules (via DBMS_RESOURCE_MANAGER or the built-in resource profiles) so that critical workloads get priority and queuing thresholds are tuned. This is the only option that directly addresses database-level concurrency and statement queuing.

Exam trap

The trap is assuming that application timeouts during concurrency spikes are an infrastructure sizing problem (compute memory, network, or OS tuning) when the actual control point in Autonomous Database is the Database Resource Manager consumer group configuration.

How to eliminate wrong answers

Option A is wrong because the physical memory of the OCI Compute host running the application has no bearing on how the Autonomous Database internally queues statements — ADB is a managed service and its resource governance is not controlled by client host sizing. Option B is wrong because Linux kernel swappiness on the database host is not customer-accessible in Autonomous Database; the service is fully managed and OS-level tuning is abstracted away. Option C is wrong because VCN security list packet drop thresholds relate to network filtering, not to database statement queuing or resource contention inside the database.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Databases questions.

Start 20-question session