Free 1Z0-1195-25 Practice Test Questions and Answers (2026)

A "MySQL Database Service DB System" includes a "Compute Instance" (A) for processing, a "Virtual

Network Interface" (B) for networking, and "Block Storage" (D) for data. "FastConnect" (C), a high-

speed connectivity service to OCI, is not a component of the DB system itself but an optional external

connection. Oracle’s MySQL Service documentation lists the core components, excluding

FastConnect.

Reference: OCI MySQL Database Service Architecture, Oracle Networking Guide.

The "Autonomous Database" offers self-service tools like "Oracle Machine Learning" (B), enabling

users to build ML models directly in the database, and "Low-Code App Dev, APEX" (C), allowing rapid

application development via Oracle APEX. "Business Objects" (A) is a third-party BI tool, not native to

ADB, and "Encryption only in Object Storage" (D) is a feature, not a tool, and inaccurate (encryption is

broader). Oracle’s documentation highlights OML and APEX as key self-service capabilities.

Reference: Oracle Autonomous Database Tools Guide, OCI Machine Learning and APEX

Documentation.

An example of an in-database option in Oracle Automated Machine Learning (AutoML) is "Oracle

Machine Learning for Python (OML4PY) APIs" (C). OML4Py enables Python-based machine learning

directly within the database, leveraging in-database algorithms for performance and security. "REST

Interface" (A) is an access method, "Cognitive text" (B) is a feature, not an algorithm type, and

"Tuning of hyperparameter" (D) is a process, not a specific option. Oracle’s documentation highlights

OML4Py as a key in-database ML tool.

Reference: Oracle Machine Learning Documentation, OML4Py User Guide.

Provisioning an "Oracle Autonomous Database" requires "Number of CPUs" (A) to define compute

resources and "Workload Type" (D) (e.g., Transaction Processing, Data Warehouse) to configure the

instance’s purpose. "Number of Tablespaces" (B) is not specified (managed automatically), and

"Backup Location FRA Size" (C) is not a user-defined parameter (backups are handled by Oracle).

Oracle’s provisioning documentation lists CPUs and workload type as mandatory.

Reference: Oracle Autonomous Database Provisioning Guide, OCI Console Setup Instructions.

The "MySQL Database Service" on Oracle Cloud Infrastructure uses "Block Volume Storage" (C) for all

data storage. Block Volume provides high-performance, persistent block storage that is directly

attached to compute instances running the MySQL database, ensuring low-latency access for

transactional and operational workloads. "Archive Storage" (A) is for long-term, infrequently

accessed data, "Object Storage" (B) is for unstructured data, and "File Storage" (D) is for shared file

systems—none of which suit the primary storage needs of a MySQL database. Oracle’s MySQL

Database Service documentation confirms Block Volume as the default storage platform.

Reference: OCI MySQL Database Service Documentation, Oracle Storage Services Overview.

The "Oracle Autonomous Database" (B) offers the highest degree of security and governance with a

self-service experience. It includes automated security features (e.g., TDE, network encryption), self-

patching, and fine-grained access controls, all managed by Oracle, while allowing users to provision

and manage databases independently. "Exadata Cloud Service" (A) provides high performance but

requires more manual oversight. "Oracle Database Cloud Service" (C) offers flexibility but less

automation, and "Oracle MySQL Database Service" (D) lacks the same level of autonomous security.

Oracle’s documentation positions Autonomous Database as the pinnacle of secure, self-service

deployment.

Reference: Oracle Autonomous Database Security Guide, OCI Database Options Overview.

In the Oracle Data Platform, the "Supply Side" refers to foundational data elements that are passively

collected and structured to provide meaning within the data ecosystem. According to Oracle’s official

documentation, the supply side includes "Business rules" (A), which define the logic and policies

governing data usage, ensuring consistency and compliance, and "Domain objects" (B), which

represent structured entities or concepts within a business domain, forming the backbone of data

modeling. "Technical definitions of business terms" (C) pertain to metadata management, and

"Reports" (D) are outputs rather than core supply-side models. Oracle’s Data Platform Foundations

emphasize business rules and domain objects as key components of the supply side for data

integration and processing.

Reference: Oracle Data Platform 2025 Foundations Associate documentation, Section on Data Supply

Side Models.

For storing application backups that need to be "stored for months, but retrieved immediately,"

"Object Storage (standard)" (A) is the suitable OCI service. Standard Object Storage offers durable,

scalable storage with immediate access, ideal for backups requiring quick retrieval. "Archive Storage"

(B) is cheaper but has retrieval delays, unsuitable for immediate access. "File Storage" (C) is for

shared file systems, and "Block Volume" (D) is for high-performance attached storage, both less

suited for long-term backups. Oracle’s OCI Storage documentation confirms Standard Object Storage

for this use case.

Reference: OCI Object Storage Guide, Oracle Backup Solutions Overview.

"Oracle Exadata Cloud Service" (B) offers expanded flexibility with shared or dedicated Exadata

infrastructure, allowing customers to choose between cost-effective shared resources or isolated

dedicated hardware for performance and compliance needs. "Oracle Database Cloud Service" (A) is

VM-based and lacks Exadata’s hardware integration, "Oracle Autonomous Database" (C) is fully

managed without hardware choice, and "Oracle Exalogic Cloud Service" (D) is an outdated

middleware platform, not database-focused. Oracle’s documentation highlights Exadata Cloud

Service’s deployment options.

Reference: Oracle Exadata Cloud Service Overview, OCI Database Options Guide.

For serverless Spark processing in Oracle’s Lakehouse architecture, "OCI Data Flow" (C) is the

designated service. OCI Data Flow is a fully managed, serverless platform that enables users to run

Apache Spark applications without managing infrastructure, making it ideal for big data processing

tasks like ETL, machine learning, and analytics. "Oracle Analytics Cloud" (A) is an analytics and

visualization tool, not a Spark processing engine. "OCI Object Storage" (B) provides scalable storage

but lacks processing capabilities, and "OCI Data Catalog" (D) is for metadata management, not Spark

job execution. Oracle’s OCI documentation confirms OCI Data Flow as the primary service for

serverless Spark workloads in the Lakehouse.

Reference: OCI Data Flow Documentation, Oracle Lakehouse Architecture Guide.

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.