Free Oracle 1z0-1195-25 Practice Exam with Questions & Answers | Set: 2

From the OCI Console for an "Oracle Autonomous Database," you can "Scale up/down CPU" (A) to adjust compute resources dynamically and "Increase Storage allocated for Database" (D) to expand capacity, both with no downtime. "Increase Network Bandwidth" (B) is not a console-adjustable parameter (managed by Oracle), and "Scale up/down Memory" (C) is not independentlyconfigurable (tied to CPU scaling). Oracle’s documentation confirms CPU and storage scaling as user-controlled actions.

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.

A prerequisite for running "APEX" (Application Express) on an Autonomous Database is provisioning "an Autonomous Database with the workload type Data Warehouse, TransactionProcessing, JSON, or APEX" (B). APEX is supported across these workload types, with ORDS (Oracle REST Data Services) pre-enabled. Option A is incorrect, as ORDS is automatically configured. Option C is too restrictive, as APEX isn’t limited to the APEX workload type alone. Option D is unnecessary, as user creation follows provisioning, not precedes it. Oracle’s Autonomous Database documentation confirms APEX availability across these workload types with no manual ORDS setup required.

The default configuration for automatic database backups in OCI (e.g., Autonomous Database) includes "Backups occur weekly" (A), with daily incremental and weekly full backups. "Archive redo log files are backed up every 30 minutes" (B) is not default (it’s real-time logging), "Retention period is set at 14 days" (C) is incorrect (default is 60 days), and "Backups are executed on primary site" (D) is vague but not a standard config statement. Oracle’s backup documentation specifies weekly full backups as default.

The "OCI Data Catalog" provides a "View of data for discovery" (D) when integrated with Autonomous Databases and OCI Object Storage in the Lakehouse solution. It serves as a metadata management service, offering a centralized view of data assets, their schemas, and relationships, enabling users to discover and understand data across the Lakehouse. "Analytic environments" (A) and "Data Warehouse" (B) refer to processing or storage constructs, not the role of Data Catalog. "Source of managed services" (C) is vague and not a documented function. Oracle’s documentation highlights Data Catalog’s role in data discovery and governance, not processing or storage.

The "MySQL Database Service" on OCI uses "Block Volume Storage" (D) for all data storage, providing high-performance, persistent block storage attached to compute instances for database operations. "Object Storage" (A) is for unstructured data, "Flash Local Storage" (B) is temporary and instance-specific, and "File Storage" (C) is for shared file systems—none suit MySQL’s needs. Oracle’s MySQL Service documentation confirms Block Volume as the standard.

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.

Oracle offers a "Dedicated cloud region" (D) as an industry-first feature to support multicloud strategies. This allows customers to run a fully managed OCI region within their own data center or a partner cloud, integrating with other providers like Azure or AWS. "Private and public cloud network" (A) is vague, "Cloud databases" (B) are common across vendors, and "Oracle FastConnect" (C) is a connectivity service, not unique to multicloud. Oracle’s documentation highlights the Dedicated Region as a pioneering multicloud solution.