Oracle Data Platform Foundations Associate flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Autonomous Database

A fully managed Oracle Database service that automates provisioning, tuning, patching, scaling, and backup, offered in Serverless and Dedicated deployments with a workload type fixed at creation.

Workload type

The choice made when creating an Autonomous Database, such as Transaction Processing, Data Warehouse, JSON, APEX, or Lakehouse, that determines default configuration and cannot be changed later.

ECPU

Elastic Compute Unit, the compute metric used by Autonomous Database Serverless; it measures database compute capacity and is billed based on consumption with optional auto-scaling.

OCPU

Oracle CPU, a compute unit equal to one physical CPU core, used to size Autonomous Database Dedicated and Base Database Service shapes and often related to ECPUs by a fixed ratio.

Auto-scaling

An Autonomous Database feature that automatically adds compute resources, up to three times the base ECPU or OCPU count, during demand spikes and releases them afterward.

Base Database Service

An OCI service providing VM or bare-metal DB systems where the customer manages the database, including patching, backups, and configuration, rather than Oracle automating those tasks.

Exadata smart scan

An Exadata capability that pushes row filtering and column projection down to storage servers, returning only relevant rows and columns to the database server to reduce I/O and CPU use.

Exascale Infrastructure

An Exadata architecture that separates and elastically scales database and storage resources, used for Exadata Database Service on Dedicated Infrastructure deployments.

Multitenant architecture

An Oracle Database design where a container database hosts multiple pluggable databases, each acting as a self-contained set of data files and metadata that can be moved or cloned.

Pluggable database

A portable database inside a multitenant container database that has its own data files and metadata and can be plugged into or unplugged from a container.

Data Guard

An Oracle disaster recovery feature that maintains standby databases synchronized with a primary through redo transport and apply, with protection modes trading availability against data loss.

Active Data Guard

A Data Guard option that opens a physical standby read-only, allowing reporting and queries to run on the standby while redo apply continues, offloading the primary.

GoldenGate

An Oracle replication product that reads transaction logs on source systems and applies changes to target systems in real time, supporting heterogeneous sources and targets with minimal source impact.

Object Storage

OCI's scalable storage for unstructured data such as CSV, JSON, and Parquet files, commonly used as a data lake landing zone that Autonomous Database can query through external tables.

DBMS_CLOUD

A PL/SQL package in Autonomous Database used to create credentials, move files to and from Object Storage, and query external files and tables directly from SQL.

External table

A database object whose metadata maps to data stored outside the database, such as files in Object Storage, allowing SQL queries without loading the data into database segments.

Partition pruning

An optimizer technique that eliminates partitions whose values cannot satisfy a query predicate, reducing the data scanned and improving performance on partitioned tables.

Automatic backup retention

Autonomous Database keeps automated backups for 60 days by default, enabling point-in-time restore and cloning within that window, with manual backups available for longer retention.

Oracle Analytics Cloud

A cloud analytics service that builds semantic models and dashboards over sources including Autonomous Database and Object Storage, adding augmented analytics and visualization.

MySQL HeatWave

A MySQL-compatible managed service with an in-memory analytics accelerator that runs transactional and analytical workloads together, including querying data lake files via HeatWave Lakehouse.

OCI IAM policy

A statement granting a group permission to perform actions on a resource type within a compartment, written as allow group name to verb resource-type in compartment name.

Compartment

A logical container in OCI used to organize and isolate resources for access control and cost tracking; IAM policies are scoped to compartments.

AI Vector Search

An Oracle Database 23ai capability adding vector data types and vector indexes so the database can perform similarity search alongside relational, JSON, and analytical queries.

JSON Relational Duality

An Oracle Database 23ai feature exposing the same underlying relational data as both relational tables and JSON documents, so applications can read and write either representation.

Autonomous Database Dedicated

A deployment option giving an isolated Exadata infrastructure with a minimum committed ECPU or OCPU capacity, chosen for isolation, residency, or compliance requirements.

Autonomous Database Serverless

A deployment option where Oracle manages the shared infrastructure, compute scales automatically, and billing is based on consumed ECPUs and storage rather than preallocated capacity.

Data lakehouse

An architecture combining data lake file storage in Object Storage with database query and management capabilities, letting SQL engines query files without a separate loading step.

Data Integration

An OCI service for building extract, transform, and load pipelines and data flows that move and transform data between sources and targets such as Object Storage and Autonomous Database.

OCI Streaming

A managed, Kafka-compatible publish-subscribe service for ingesting continuous event and log data in real time for downstream processing and analysis.

Maximum Availability

A Data Guard protection mode that commits transactions when redo is written to at least one synchronized standby, preserving availability while limiting potential data loss.

Maximum Protection

A Data Guard protection mode that commits transactions only after redo is confirmed on a synchronized standby, guaranteeing zero data loss but risking primary shutdown if no standby is reachable.

Autonomous Database cloning

Creating a copy of an Autonomous Database from a running instance or a backup, useful for testing, development, or restoring data to a prior point in time.