1Z0-1093-25 Oracle Cloud Database Services 2025 Professional Practice Questions

The dcli utility is specifically designed to execute commands and scripts in parallel across multiple database nodes in a cluster. The DBA would use a command like dcli -g all_nodes -l user /usr/local/bin/diag.sh to achieve the desired outcome, making it the correct tool for this task.

This is the correct answer. Database backups can generate a massive amount of network traffic. By directing this traffic over a dedicated Backup Network to services like Object Storage, it prevents the Client Network from becoming saturated. This ensures that application performance and client connectivity are not negatively impacted during backup operations.

This is correct. OCPU scaling on Exadata is an elastic, online operation. The change takes effect without requiring downtime. For 'License Included' models, billing is metered hourly, so the increased cost for the additional OCPUs starts as soon as they are provisioned. For BYOL, the customer must ensure they have sufficient licenses to cover the new, higher OCPU count.

This statement is correct. Exadata Cloud Service shapes are fixed hardware configurations. While you can elastically scale OCPUs within the provisioned hardware, you cannot elastically add more physical DB servers or storage servers to the configuration. Increasing the physical hardware requires provisioning a new, larger shape and migrating the databases.

Database Resource Manager is the correct feature for this requirement. Within a multitenant environment, you can create a CDB resource plan that allocates CPU shares or utilization limits to different PDBs. The architect can create a plan that gives the 'Gold' PDB a higher share, ensuring it gets its required resources, especially during periods of contention.

HeatWave Lakehouse is the exact feature designed for this scenario. It allows the HeatWave query engine to directly query data in various formats (like Parquet and CSV) residing in OCI Object Storage at massive scale. This enables users to analyze data in their data lake and join it with transactional data in the MySQL database within a single query, without requiring any ETL process.

Using the EXPLAIN command is the standard way to see the query execution plan. When a query is successfully offloaded to HeatWave (codenamed RAPID), the Extra column of the EXPLAIN output will contain the note 'Using secondary engine RAPID'. If this note is absent, the query was executed by the standard MySQL engine (InnoDB), which explains the poor performance for an analytical query.

Security Lists control traffic at the subnet level. An ingress rule with a source CIDR that is too broad (e.g., the entire VCN CIDR block 10.0.0.0/16 instead of a specific application tier subnet) is the most common reason for unintended access from other subnets within the same VCN. This directly addresses the problem of intra-VCN exposure.

This is the most effective cost-saving strategy. Recent backups, which are more likely to be needed for operational recovery, remain in the instantly accessible Standard tier. Older backups are automatically moved to the much cheaper Archive tier for long-term retention. This perfectly balances accessibility for recent data with cost efficiency for archival data, directly addressing the company's requirements.

Maximum Availability mode uses synchronous redo transport, ensuring zero data loss if the primary database fails, thus meeting the near-zero RPO requirement. It prioritizes data protection without halting the primary if the standby becomes unavailable.

Data Guard requires a standby database to which redo data is shipped. For cross-region DR, this standby database must be provisioned on a DB System in the designated DR region, ready to take over in a failover event.