Oracle Database@AWS Architect Professional flashcards

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

ODB network

A customer-owned network construct in Oracle Database@AWS that is associated with a VPC and provides private connectivity between the VPC and the Exadata infrastructure.

Exadata infrastructure

The Oracle-managed physical Exadata resource in an AWS Availability Zone that contains database servers and storage servers and hosts one or more VM clusters.

VM cluster

A logical grouping of database and storage servers within Exadata infrastructure that runs Oracle Grid Infrastructure and hosts Oracle databases; it is created after the infrastructure.

RAC on Exadata

Oracle Real Application Clusters configured across database servers in one Exadata infrastructure, providing instance failover within a single Availability Zone.

Cross-AZ Data Guard

An Oracle Data Guard standby database on separate Exadata infrastructure in a second Availability Zone or Region, protecting against the loss of the primary Availability Zone.

BYOL licensing

Bring-your-own-license model in which the customer uses existing Oracle Database licenses for databases on Oracle Database@AWS instead of license-included pricing.

Provisioning order

The dependency sequence for Oracle Database@AWS: ODB network first, then Exadata infrastructure, then VM cluster, then Oracle database; each child requires its parent to be available.

Maintenance window

A customer-selected time range during which Oracle applies infrastructure and Grid Infrastructure patches to Oracle Database@AWS resources without unexpected disruption.

Exadata shape selection

The choice of Exadata configuration, such as quarter, half, or full rack equivalent, that determines the number of database and storage servers provisioned at infrastructure creation.

Database creation parameters

Settings such as database name, unique name, Oracle home, edition, character set, and storage size that are fixed when the database is created and generally require recreation to change.

Private connection status

The state of the link between the customer VPC and the ODB network; it must be Available before applications can connect to databases on the Exadata infrastructure.

ODB network CIDR

The IP address range assigned to the ODB network at creation; it must not overlap with the VPC or peered networks and must be large enough for SCAN and node addresses.

Security group boundary

AWS security groups applied at the VPC and ODB network boundary that restrict which source addresses and ports, such as listener port 1521, can reach the database.

IAM versus database roles

AWS IAM controls ODB API actions such as create and delete, while Oracle database users and roles control data access; the two authorization planes operate independently.

Enterprise User Security

An Oracle Database feature that centralizes database user authentication and authorization in a directory such as AWS Managed Microsoft AD, reducing database-local accounts.

KMS encryption at rest

Default encryption of Oracle Database@AWS data using AWS KMS keys; customer-managed keys can be selected at provisioning to control rotation and revocation.

CloudTrail and Unified Auditing

CloudTrail records ODB API calls while Oracle Unified Auditing records database activity; both are needed for a complete operational and security audit trail.

No internet gateway route

A network isolation rule stating that the ODB network should not be routed to an internet gateway; database traffic should arrive privately from associated or peered VPCs.

RMAN backup target

An object storage or backup destination reachable from the ODB network where Oracle Recovery Manager writes database backups for restore and point-in-time recovery.

Data Pump migration

A migration method using Oracle Data Pump export and import to move schemas or databases from on-premises or another cloud into Oracle Database@AWS.

GoldenGate replication

An Oracle replication tool used for ongoing change capture during migration, enabling a short cutover with minimal downtime to Oracle Database@AWS.

Compute and storage scaling

Adding database servers changes compute capacity while adding storage servers changes storage capacity; the two are scaled independently and may require maintenance actions.

Decommissioning order

The reverse of provisioning: drop or migrate databases, delete the VM cluster, then the Exadata infrastructure, then the ODB network; parents cannot be deleted before children.

CloudWatch infrastructure metrics

AWS CloudWatch receives infrastructure-level metrics exposed by Oracle Database@AWS, complementing Oracle Enterprise Manager for database-level monitoring.

Oracle-managed patching

Oracle applies Exadata infrastructure and Grid Infrastructure patches during the maintenance window, while database patches remain the customer's or automation's responsibility.

AZ failure protection

Protection against loss of an Availability Zone requires a Data Guard standby on separate Exadata infrastructure; RAC alone only protects against instance failure within one AZ.

Shared storage performance

Exadata storage performance is shared across all databases on the same infrastructure, so sizing must aggregate peak IOPS and throughput across those databases.

Grid Infrastructure image

The Oracle Grid Infrastructure software version and image selected when creating a VM cluster; it determines the clusterware and ASM version running on that cluster.

SSH key pair

A key pair supplied at VM cluster creation that enables secure shell access to cluster nodes for authorized administrative tasks.

Tagging consistency

Applying a consistent AWS tag scheme to ODB resources for cost allocation and access control, separate from any Oracle-side tags used inside the database.

SCAN VIP address planning

Reserving enough addresses in the ODB network CIDR for Single Client Access Name VIPs, node IPs, and RAC VIPs so clients can connect without hard-coded node addresses.

Private connectivity requirement

Database client traffic reaches Oracle Database@AWS through a private connection between the VPC and ODB network, not through the public internet.