1z0-1195-25 Practice Questions

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.

When registering "Exadata Cloud@Customer" in an OCI region, you must "consider any business policies or regulations that preclude the use of a particular region" (A), as compliance (e.g., data residency laws) dictates region selection. You should also "consider the physical proximity of the region you register the infrastructure into your data center" (D), as proximity reduces latency for control plane interactions. Option B is false because, despite being hosted on-premises, Exadata Cloud@Customer is registered in an OCI region for management. Option C is incorrect, as the region cannot be changed post-creation without significant reconfiguration. Oracle’s documentation highlights these considerations for region selection.

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.

Oracle’s Data Management strategy aims to deliver "the fastest, most scalable converged SQL database" (A), exemplified by its Autonomous Database and Exadata systems, which support multiple data types and workloads efficiently. It also seeks to "automate everything for developers, data analysts, DBAs, and data scientists" (B), leveraging self-managing, self-tuning capabilities to reduce manual effort and enhance productivity. Option C ("multiple integration points for 3rd party databases") is not a primary objective, as Oracle focuses on its own ecosystem. Option D ("best platform for warehouse workloads only") is too narrow, as the strategy spans beyond just warehousing to include transactional, analytical, and JSON workloads. Oracle’s official data management documentation emphasizes speed, scalability, and automation as core goals.