Oracle 1Z0-1195-26 Practice Exam Questions & Answers

In Oracle's Data Lakehouse architecture, data persistence refers to the storage layer where data is durably maintained. 'Autonomous Database' (B) provides a managed, self-tuning relational database for structured data persistence, supporting SQL-based workloads. 'OCI Object Storage' (D) offers scalable, durable storage for unstructured and semi-structured data, such as files, images, and logs, serving as the data lake component of the Lakehouse. 'OCI Data Catalog' (A) is a metadata management service, not a persistence layer, and 'OCI GoldenGate' (C) handles data replication and integration, not direct storage. Oracle's Lakehouse documentation identifies Autonomous Database and OCI Object Storage as the primary persistence services.

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.

The most important reason to upgrade and patch is 'Security' (A). Patches address vulnerabilities, protecting against exploits and ensuring compliance, which outweighs 'Fix bugs' (C) in priority. 'Restructure the database' (B) is unrelated to patching, and 'Upgrading and patching the database is not important' (D) is false. Oracle's security guidelines prioritize patching for protection.

'Exadata' integrates software and hardware and is available both 'In the Oracle Cloud and customer site' (D). It is offered as Exadata Cloud Service (public cloud) and Exadata Cloud@Customer (on-premises), providing flexibility for hybrid deployments. 'Only in a hybrid cloud' (A) is too restrictive, 'Only in public cloud environments' (B) ignores Cloud@Customer, and 'Only at the customer site' (C) excludes the cloud option. Oracle's documentation confirms Exadata's availability in both OCI and on-premises configurations.

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.

When provisioning an 'Autonomous Database' on Oracle Cloud Infrastructure, the supported workload types include 'JSON' (B) for document-centric applications, 'Data Warehouse' (C) for analytics, and 'APEX' (D) for low-code application development, alongside Transaction Processing (not listed here). 'MySQL' (A) is not a workload type for Autonomous Database; instead, it is a separate database service (Oracle MySQL Database Service) on OCI, not part of the Autonomous Database offering. Oracle's documentation specifies the distinct workload options available during Autonomous Database provisioning, excluding MySQL.

'SQLcl (including Liquibase)' (D) is the tool provided to support CI/CD workflows. SQLcl integrates with Liquibase to track, version, and deploy database schema changes, aligning with CI/CD pipelines. 'ADB console' (A) is for monitoring, 'Database Actions' (B) is for SQL tasks, and 'SQL Developer' (C) is a GUI tool, none of which are CI/CD-focused. Oracle's documentation highlights SQLcl's Liquibase integration for DevOps workflows.