The Exadata X8M leverages "Remote Direct Memory Access" (RDMA) to access "Persistent Memory"

(B). RDMA allows direct memory-to-memory data transfer between systems without CPU

involvement, enhancing performance. In Exadata X8M, RDMA accesses persistent memory (PMEM)

to accelerate database operations by reducing latency and improving I/O throughput. "Compute

Instances" (A) and "Database Servers" (D) are broader entities, not the specific resource RDMA

targets, while "Storage Disks" (C) are traditional storage, not memory. Oracle’s Exadata

documentation highlights RDMA’s use with persistent memory in X8M systems.

Reference: Oracle Exadata X8M Technical Overview, OCI Hardware Innovations.

Two important reasons to upgrade and patch are "Support Compliance" (A), ensuring the database

remains under Oracle’s support policy with access to updates, and "Security" (C), applying patches to

mitigate vulnerabilities and protect data. "Validation of application" (B) is a byproduct, not a primary

reason, and "Restructure the database" (D) is unrelated to patching. Oracle’s maintenance guides

emphasize compliance and security as key drivers.

Reference: Oracle Patching Best Practices, OCI Security Maintenance Guide.

The "Autonomous JSON Database" supports NoSQL-style document access through "SODA" (Simple

Oracle Document Access) APIs (B). SODA provides a simple, intuitive interface for developers to

interact with JSON documents stored in the database using operations like insert, query, and update,

without requiring SQL knowledge. Options A ("OASD"), C ("DOSA"), and D ("OSDA") are not

recognized API sets in Oracle’s documentation. SODA is explicitly documented as the standard NoSQL

API for Autonomous JSON Database, aligning with Oracle’s converged database strategy to support

multiple data models.

Reference: Oracle Autonomous JSON Database Documentation, SODA Developer Guide.

The Oracle Cloud and Microsoft Azure interconnect offers "Low Latency" (B), achieved through a

high-speed, private connection between OCI and Azure data centers, reducing delays for cross-cloud

workloads. It also provides "Unified identity and access management" (C), integrating Oracle IAM

with Azure Active Directory for seamless user authentication. "Upgrade compliance" (A) is vague and

not a documented benefit, while "Connection to other multicloud environments" (D) is not specific

to this partnership. Oracle’s multicloud documentation highlights latency and identity integration as

key advantages.

Reference: Oracle-Azure Interconnect Guide, OCI Multicloud Partnership Overview.

For an "Autonomous Database," the DBA can "Open the database in OCI Console and increase the

number of OCPU. No downtime required" (C). Autonomous Database supports dynamic scaling of

OCPUs online, with no service interruption, leveraging its self-managing capabilities. Options A and B

involve unnecessary downtime, and D adds an unneeded user restriction. Oracle’s documentation

confirms zero-downtime OCPU scaling as a key feature.

Reference: Oracle Autonomous Database Scaling Guide, OCI Console Documentation.