Oracle Data Platform Foundations Associate key terms

A cloud database service that provisions, tunes, patches, and scales itself with minimal manual administration, offered in transaction processing and data warehouse workload flavors.

An Autonomous Database workload type optimized for analytic queries and bulk loads, using columnar processing and automatic indexing rather than manual tuning.

An Autonomous Database workload type tuned for high-concurrency transactional workloads such as order entry, with row-based access and automatic index management.

A managed Oracle Database offering on dedicated Exadata infrastructure in OCI, giving full administrative control plus smart storage offload for demanding workloads.

A managed Oracle Database service on virtual machines in OCI that provides database administration control without requiring Exadata hardware.

A multitenant architecture root database that hosts one or more pluggable databases, sharing background processes and memory while isolating each tenant's data dictionary.

A self-contained set of data files and metadata that plugs into a container database, allowing many tenants to share one instance while remaining logically separate.

An Oracle Database design in which a single instance serves multiple pluggable databases, reducing overhead and simplifying consolidation and patching.

Oracle's public cloud platform supplying compute, storage, networking, and managed database services organized into regions and availability domains.

A geographically distinct area containing one or more availability domains where Oracle Cloud Infrastructure resources are deployed and data residency is determined.

An isolated data center grouping within an OCI region with independent power and network, used to spread resources for fault tolerance.

A grouping of hardware within a single availability domain that shares no single point of failure with other fault domains, used for anti-affinity placement.

A logical grouping of OCI resources used to organize, isolate, and control access, forming the boundary at which identity policies are typically granted.

The root OCI account that owns all resources, users, and compartments created by an organization, identified by its own unique namespace.

The OCI service that authenticates users and authorizes actions through policies written in a human-readable policy language over compartments and resource types.

A rule-based collection of OCI compute or service instances whose membership is determined by matching attributes, enabling policies for workloads without stored credentials.

An identity that lets an OCI compute instance call other OCI services using certificates, authorized through policies that reference its dynamic group.

An identity assumed by an OCI managed resource, such as a serverless function, so it can access other services without embedding user credentials.

An OCI service for storing unstructured data as objects inside buckets, addressed by name, with tiering options for cost control.

A logical container in OCI Object Storage that holds objects and defines namespace-level settings such as visibility, versioning, and lifecycle rules.

Network-attached durable storage presented to a compute instance as a disk, used for database files and other low-latency persistent storage needs.

A shared, hierarchical network file system service in OCI that multiple compute instances can mount concurrently for shared application data.

A software-defined private network in OCI containing subnets, route tables, gateways, and security rules that control traffic for attached resources.

A contiguous range of IP addresses within a virtual cloud network, scoped to one availability domain or regional, that hosts instances and other resources.

A set of stateless ingress and egress rules applied at the subnet level in OCI to permit or deny traffic to attached resources.

A stateful set of traffic rules applied to selected virtual network interface cards rather than whole subnets, giving finer-grained control.

A dedicated private network connection between an on-premises data center and OCI that avoids the public internet and offers predictable latency.

A deployment option where Oracle fully manages the underlying infrastructure, with compute and storage scaled independently and billed by consumption.

A feature that automatically adds compute resources to a running database when workload demand rises, then releases them when demand falls.

A group of Autonomous Databases that share a pool of compute resources, allowing capacity to be allocated where needed and lowering total cost.

An Oracle high-availability feature that maintains standby databases synchronized with a primary, enabling fast failover and disaster recovery.

A copy of a primary database kept current by redo transport, ready to take over if the primary becomes unavailable.

The practice and tooling of copying database data and logs so it can be restored after corruption, deletion, or site loss, with defined retention.

Restoring a database to a specific past moment by applying archived redo logs to a backup, used to undo accidental changes.

A centralized repository storing raw structured, semi-structured, and unstructured data at scale, typically on object storage, before transformation.

A curated analytical repository holding integrated, subject-oriented, historical data modeled for reporting and decision support rather than transactions.

A focused subset of a data warehouse serving one department or business function, often modeled as a star schema.

A dimensional model with a central fact table of measures referencing surrounding dimension tables that describe the business entities.

A table storing quantitative business events or measures plus foreign keys to dimensions, usually the largest table in a star schema.

A table of descriptive attributes, such as product or customer details, that provides context for the measures stored in a fact table.