Free 1Z0-1093-25 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

In the Oracle Cloud Infrastructure (OCI) shared responsibility model for the Base Database Service on virtual machines (VMs), the customer has full administrative (root or opc) access to the VM. Consequently, the customer is responsible for managing the entire software stack within the guest OS. This includes the lifecycle management of the Oracle Grid Infrastructure and the Oracle Database software, which involves tasks like patching, upgrades, and configuration. Oracle's responsibility ends at the hypervisor layer, as it manages the underlying physical hardware, network, and virtualization.

A. Oracle is responsible for the fault tolerance and maintenance of the underlying physical hardware infrastructure in its data centers as part of the IaaS offering.

C. The hypervisor is a core component of the OCI virtualization infrastructure, which is exclusively managed and maintained by Oracle.

D. The customer is responsible for OS patching. OCI does not automatically apply patches; the customer must initiate or configure automated patching using OCI tools.

1. Oracle Cloud Infrastructure Documentation, "Overview of the Base Database Service": In the section "Customer and Oracle Responsibilities," it is stated: "You have root or opc access to the virtual machine, so you are responsible for managing the operating system and the database." This management scope includes the Oracle Grid Infrastructure.

2. Oracle Cloud Infrastructure Security Guide, "Shared Security Responsibility Model": The security guide provides diagrams and descriptions that clearly delineate responsibilities. For services like Base Database Service (categorized under IaaS/PaaS), the customer is shown to be responsible for the "Operating System," "Middleware," and "Runtime," which encompass the Oracle Grid Infrastructure. Oracle's responsibility is for the "Virtualization," "Servers," "Storage," and "Networking" layers.

The primary function of the Oracle NoSQL Database Cloud Service SDK (Software Development Kit) is to provide a high-level, language-specific programming interface for developers. It simplifies application development by abstracting the complexities of the underlying REST API. The SDK handles low-level details such as request signing for authentication, data serialization/deserialization, and retry logic for transient errors. This allows developers to perform data (CRUD) and table (DDL) operations using familiar programming constructs in languages like Java, Python, or Go, rather than manually constructing and managing raw HTTP requests.

A. Physical storage layout is an internal detail managed entirely by the Oracle Cloud service, not controlled by a client-side SDK.

C. Underlying infrastructure (e.g., servers, storage) is managed through Oracle Cloud Infrastructure (OCI) control plane tools like the Console, CLI, or Terraform, not the data-focused NoSQL SDK.

D. Network security policies are configured at the OCI platform level using services like Identity and Access Management (IAM) and Virtual Cloud Network (VCN), not via the application SDK.

1. Oracle Cloud Infrastructure Documentation, "About the Oracle NoSQL Database Cloud SDKs": "The Oracle NoSQL Database Cloud SDKs provide interfaces for developing applications that use the Oracle NoSQL Database Cloud Service. The SDKs are built on top of the Oracle Cloud Infrastructure SDKs and provide a higher-level interface to the Oracle NoSQL Database Cloud Service." This source confirms the SDK's role as a high-level programming interface for application development.

2. Oracle NoSQL Database Cloud Service Developer Guide, "Overview of APIs": "The Oracle NoSQL SDKs provide a higher-level, easy-to-use API that lets you develop applications. The SDKs are built on top of the Oracle Cloud Infrastructure (OCI) SDKs and use the OCI infrastructure for authentication and request signing. The SDKs simplify the process of writing code to work with the service by providing pre-written code that handles tasks such as request signing, retries, and error handling." This directly supports the abstraction of low-level details (Option B) and refutes the management of infrastructure or security (Options C and D).

The exadcli list metricdetail command is used to display the detailed attributes of metric definitions, including their name, object type, unit, and description. Using the -cell option correctly targets the storage cells. The -metricname "flashcache." argument employs a wildcard to specifically select all metrics related to the Smart Flash Cache. This combination provides the most comprehensive and detailed information about all available flash cache statistics (reads, writes, hits, misses, etc.), directly addressing the question's requirement for detailed and comprehensive data on flash cache usage.

A. list metriccurrent ... "IOPS,MBPS" is too general; it retrieves only the current values for overall I/O and does not specifically detail Smart Flash Cache metrics.

C. list metriccurrent ... "cell." is too broad, retrieving current values for all cell metrics, not just the detailed flash cache statistics requested.

D. list metrichistory retrieves historical data for specific metrics, not a comprehensive overview of all available flash cache metric definitions and their current details.

1. Oracle Exadata Database Machine Maintenance Guide, 23c.

Reference: Chapter 10, "Exadata Management Command-Line Interface (EXADCLI)", Section: "EXADCLI Commands".

Details: This section describes the LIST METRICDETAIL command, stating it "displays the detailed attributes of a metric definition." It also explains the use of wildcards for metric names, confirming that flashcache. is a valid way to query all related metrics.

2. Oracle Cloud Infrastructure Documentation, Exadata Database Service on Dedicated Infrastructure.

Reference: "Use the EXADCLI Utility", Section: "EXADCLI Command Reference".

Details: The documentation specifies that list metricdetail provides comprehensive attributes for metrics. It provides examples of querying cell metrics, such as exadcli -e "list metricdetail where objecttype='CELL' and name like 'FC.'", which is functionally equivalent to the command in option B and targets Flash Cache (FC) metrics.

The Oracle Cloud Infrastructure (OCI) Data Transfer Service is the officially recommended method for securely and efficiently migrating large volumes of data (typically terabytes or more) to OCI. This service is specifically designed to overcome the challenges of slow, unreliable, and expensive network transfers for bulk data. It uses ruggedized, encrypted physical storage appliances that are shipped to your location. You load your backup data onto the appliance, and Oracle securely uploads it directly into your OCI Object Storage tenancy, from where it can be loaded into MySQL HeatWave.

A. Transferring the backup files directly over the public internet using FTP.

FTP is an insecure protocol that transmits credentials in cleartext. Furthermore, public internet transfers for large files are often slow and unreliable.

B. Shipping physical hard drives containing the backup files to the OCI data center.

This describes the general concept, but OCI provides a specific, managed, and secure service for this process, which is the Data Transfer Service (Option C).

D. Creating a secure VPN connection and transferring the backup files using scp.

While secure, this method is often impractical for very large backups due to network bandwidth limitations and the significant time required for the transfer.

E. Use of Data Pump with a database link.

Oracle Data Pump is a utility for Oracle Database, not MySQL. The equivalent tools for MySQL would still face network transfer limitations for large datasets.

1. Oracle Cloud Infrastructure Documentation, "Overview of Data Transfer." This document states, "Oracle Cloud Infrastructure Data Transfer is a data migration service that lets you securely move petabyte-scale datasets from your data center to Oracle Cloud Infrastructure... Use Data Transfer when you want to migrate a large volume of data to the cloud and uploading over the public internet is not feasible or practical." (Oracle Cloud Infrastructure Documentation, Data Transfer, Concepts, overview.htm)

2. Oracle Cloud Infrastructure Documentation, "Migrating from On-Premises MySQL to MySQL HeatWave." While this guide focuses on tools like MySQL Shell, the prerequisite for large-scale migration is often to have the data available in OCI Object Storage. The Data Transfer Service is the primary method for this initial bulk data seeding. The migration process then proceeds by loading data from Object Storage. (Oracle Cloud Infrastructure Documentation, MySQL HeatWave, Section: Migrating from On-Premises MySQL)

3. Oracle Solution Brief, "OCI Data Transfer Options." This document compares various data transfer methods and explicitly recommends the Data Transfer Service for "Bulk data transfer" and "Initial data seeding," especially for datasets larger than a few terabytes where network transfer would take too long. (Oracle Cloud Infrastructure, OCI Data Transfer Options Solution Brief, Page 2, "Use Cases")

A key-value NoSQL database is designed around a simple data model consisting of a unique key paired with an associated value. The primary and most efficient method for data retrieval is a direct lookup using this unique key. The database is optimized for this specific operation, providing low-latency reads and writes by avoiding the overhead of complex query processing, relationship traversal, or full table scans. This model treats the value as an opaque blob, and access is predicated on knowing the key beforehand.

A. Using SQL queries is the primary mechanism for relational databases, not key-value stores, which typically use simple get/put/delete APIs.

C. Traversing relationships between nodes is the defining characteristic of a graph database, which models data as nodes and edges.

D. Scanning all documents is an inefficient access method, though possible. The primary access pattern in document stores is typically via an index or primary key, similar to a key-value store.

1. Oracle NoSQL Database Documentation: "Oracle NoSQL Database is a key-value database... In a key-value store, the application stores its data using a key. It can then retrieve the data from the store using that same key. The store itself does not care what the data is; it just stores it."

Source: Oracle NoSQL Database, Administrator's Guide, Release 23.1, Chapter 1, "Introduction to Oracle NoSQL Database".

2. Oracle Cloud Infrastructure Documentation: "The Oracle NoSQL Database Cloud Service is built upon the Oracle NoSQL Database, which uses a key-value data model... Applications use a key to retrieve an associated value. This direct key-based access ensures extremely low latency for read and write operations."

Source: Oracle Cloud Infrastructure Documentation, "Overview of NoSQL Database Cloud Service", Data Models section.

3. University Courseware: "The simplest NoSQL data store is the key-value store... The API for a key-value store is very simple: insert(key, value), fetch(key), update(key, value), and delete(key). The primary access is by the key."

Source: Stanford University, CS 245: Principles of Data-Intensive Systems, Lecture Notes on NoSQL Databases.

In Oracle NoSQL Database Cloud Service, performance and cost are managed by provisioning capacity for each table. This capacity is defined by three main limits: Read Units, Write Units, and Storage capacity. The question specifically asks for rate limits, which govern the throughput of operations. These are directly controlled by setting the number of Read Units and Write Units. A Read Unit corresponds to one eventually consistent read per second for a row up to 1 KB, while a Write Unit corresponds to one write per second for a row up to 1 KB. These two dimensions, read and write throughput, are the primary rate limits users configure.

A. Storage capacity is a limit based on size (GB), not a rate or throughput limit. Network bandwidth is managed by the service, not a user-configured table limit.

C. CPU and memory are underlying infrastructure resources managed by the Oracle Cloud service, not dimensions directly provisioned by the user on a per-table basis.

D. The number of indexes is a structural limit, not a rate limit. Query complexity influences the consumption of Read Units but is not a provisioned limit itself.

1. Oracle Cloud Infrastructure Documentation, "Estimating Capacity for Oracle NoSQL Database Cloud Service":

Section: "Provisioning Capacity": "You provision capacity for Oracle NoSQL Database Cloud Service tables by specifying throughput and storage values. Throughput capacity is specified in terms of Read Units and Write Units."

Section: "Read and Write Units": This section explicitly defines Read Units and Write Units as the measures for read and write throughput, respectively.

2. Oracle Cloud Infrastructure Documentation, "Service and Table Limits for Oracle NoSQL Database Cloud Service":

Section: "Table Limits": This section lists the default and maximum limits for "Max Read Units" and "Max Write Units" per table, reinforcing that these are the fundamental, configurable throughput dimensions. It also lists "Max Storage (GB)" separately, distinguishing it from the rate limits.

The Performance Hub in Oracle Database Management is a comprehensive tool for monitoring database performance. Its main interface prominently features the Average Active Sessions (AAS) chart, which provides an overview of the database workload. Within the Performance Hub, the Real-Time SQL Monitoring feature allows for detailed analysis of long-running SQL statements. When examining a specific monitored SQL statement, the details page includes granular I/O statistics, one of which is Physical Reads. Therefore, both AAS (at the hub level) and Physical Reads (at the specific SQL level) are metrics available while using this feature.

C. Number of CPUs on the host: This is static host configuration information, not a real-time performance metric monitored for a SQL statement within Performance Hub.

D. Database Version: This is static database identification information and is not a performance metric displayed in the Real-Time SQL Monitoring feature.

1. Oracle Cloud Infrastructure Documentation, Database Management, "Monitor and Tune a Managed Database with Performance Hub": This document describes the main components of the Performance Hub. The section "About the Performance Hub UI" explicitly states, "The time series chart shows the Average Active Sessions (AAS) data..." This confirms that AAS is a primary metric available in the interface where SQL Monitoring is performed.

2. Oracle Cloud Infrastructure Documentation, Database Management, "Monitor SQL Statements in Real-time": This document details the Real-Time SQL Monitoring feature. In the section describing the "Monitored SQL Details" page, under the "Details" tab, it lists the available metrics. The "I/O" subsection includes metrics such as "I/O Requests," "I/O Bytes," and explicitly mentions "Physical Reads" as a monitored statistic for the SQL execution. This directly confirms Physical Reads is an available metric.

The creation and management of Oracle Cloud Infrastructure (OCI) resources, such as a MySQL HeatWave Database Service System, are performed through OCI's control plane interfaces. The OCI Console is the primary web-based graphical user interface for provisioning and managing all OCI services. The OCI Command Line Interface (CLI) is a tool that provides the same core capabilities as the Console, enabling users to create and manage resources through commands, which is ideal for automation and scripting. Both are officially supported methods for creating a HeatWave DB System.

C. OCI Bastion Server: An OCI Bastion is a service that provides secure, session-based access to private resources. It is used for connectivity, not for provisioning or creating infrastructure.

D. MySQL Shell on OCI Compute: MySQL Shell is an advanced client and code editor for MySQL. It is used to connect to and manage an existing database, not to create the underlying DB System infrastructure.

E. OCI SQL Developer: OCI SQL Developer (or SQL Developer Web) is a database development and administration tool. Like MySQL Shell, it is used to interact with a database after it has been provisioned.

1. Oracle Cloud Infrastructure Documentation, MySQL HeatWave, "Creating a DB System": This document explicitly states, "You can create a DB system using the Console, CLI, or API." It then provides detailed instructions for using the OCI Console.

Source: Oracle Cloud Infrastructure Official Documentation, "Creating a DB System", Section: "Using the Console".

2. Oracle Cloud Infrastructure Documentation, CLI Reference, "oci mysql db-system create": This official CLI command reference details the syntax and parameters for the create command, which provisions a new MySQL DB System, including the option to specify a HeatWave shape.

Source: Oracle Cloud Infrastructure CLI Command Reference, mysql db-system section, create command.

3. Oracle Cloud Infrastructure Documentation, Bastion, "Overview of Bastion": This document describes the Bastion service's purpose: "Bastion provides restricted and time-limited secure access to target resources that don't have public endpoints." This confirms it is an access tool, not a creation tool.

Source: Oracle Cloud Infrastructure Official Documentation, "Overview of Bastion".

The primary architectural trade-off for many NoSQL databases is rooted in the CAP theorem, which states a distributed system can only simultaneously provide two of three guarantees: Consistency, Availability, and Partition Tolerance. To achieve massive horizontal scalability and high availability across distributed nodes, NoSQL systems must handle network partitions. Consequently, they often relax the strict, immediate consistency (ACID properties) typical of relational databases in favor of an eventual consistency model (BASE). This allows the system to remain available for reads and writes even if some nodes are temporarily disconnected, a key requirement for large-scale, fault-tolerant applications.

A. NoSQL databases typically relax, rather than strengthen, data consistency compared to relational databases, which are designed for strong consistency.

C. Relational databases, with their rigid schemas and ACID transactions, are generally considered superior for data integrity in traditional transactional systems.

D. NoSQL databases use a variety of query languages and APIs (e.g., key-value, document, graph); they do not universally use standard SQL.

1. Oracle NoSQL Database Administrator's Guide, Release 23.1: In the "Consistency Guarantees" section, the documentation details various consistency policies that can be specified by the application, such as Consistency.NONEREQUIRED (eventual consistency) and Consistency.ABSOLUTE (strong consistency). This configurability highlights that sacrificing strong consistency is a fundamental design choice to gain other benefits like lower latency. (See Chapter 5: Application Development Concepts -> Consistency Guarantees).

2. Gilbert, S., & Lynch, N. (2002). Brewer's conjecture and the feasibility of consistent, available, partition-tolerant web services. ACM SIGACT News, 33(2), 51–59. This foundational academic paper provides the formal proof of the CAP theorem, which mathematically underpins the trade-off between consistency and availability in distributed systems like NoSQL databases. (DOI: https://doi.org/10.1145/564585.564601).

3. Oracle White Paper: "An Introduction to Oracle NoSQL Database": This document often explains the design philosophy, stating, "Oracle NoSQL Database is designed for massive scale, high availability, and predictable low latency," which are the benefits gained by making flexible trade-offs on the consistency spectrum, a core difference from traditional RDBMS architectures. (Refer to sections on Architecture and Data Consistency Models).

Oracle Data Guard is the primary solution for ensuring high availability and minimizing downtime during planned maintenance. A switchover is a planned and controlled role reversal between a primary database and its standby counterpart. This operation allows the production workload to be seamlessly transferred to the standby database. Consequently, maintenance activities such as patching or upgrades can be performed on the original primary system without interrupting the database service. This makes the switchover operation the most direct lifecycle management activity for ensuring continued availability during a planned maintenance window, aligning with Oracle's Maximum Availability Architecture (MAA) best practices.

A. Taking a full database backup using RMAN is a disaster recovery preparation task, not a method for maintaining live service availability during maintenance.

B. Performing an in-place upgrade of the database software inherently requires downtime to stop, patch, and restart the database, which is the opposite of ensuring availability.

D. Applying a quarterly security patch is the maintenance activity itself, which necessitates a strategy like Data Guard to avoid downtime; it does not ensure availability on its own.

E. Resizing block volume storage is a specific infrastructure task; it is not the general mechanism used to maintain availability during broader database software maintenance.

1. Oracle Cloud Infrastructure Documentation, High Availability for Base Database Service: "For planned maintenance, you can use Oracle Data Guard to minimize or eliminate downtime. A switchover is a role reversal between a primary database and one of its standby databases. A switchover ensures no data loss and is typically used for planned maintenance of the primary system." (Section: Oracle Data Guard for High Availability)

2. Oracle Database Documentation, Data Guard Concepts and Administration, 23c, Chapter 5, "Role Transitions": "A switchover is a role transition between a primary database and a standby database. A switchover is a planned event that is typically initiated for planned maintenance of the primary system. During a switchover, the primary database transitions to a standby role, and the standby database transitions to the primary role." (Section 5.1, Introduction to Role Transitions)

3. Oracle White Paper, Oracle Maximum Availability Architecture (MAA) - Oracle Database 19c: "Oracle Data Guard is the foundation of Oracle’s Maximum Availability Architecture... For planned maintenance, Data Guard enables role transitions (switchover) to a synchronized physical standby database, allowing maintenance to be performed on the primary system while the production application remains available." (Section: Planned Maintenance, Page 11)

When applying an Oracle-provided patch to an Exadata Database Service instance via the Oracle Cloud Infrastructure (OCI) console, the process is designed to be comprehensive and maintain high availability. The patch bundles typically include updates for the operating system (OS), Grid Infrastructure, and database software. The update is applied to the database (compute) nodes in a rolling fashion, meaning one node is patched and restarted at a time. This strategy ensures that the database service remains available throughout the process, thus minimizing downtime. The patching of the storage server nodes is a separate, distinct operation also managed from the OCI console.

A. Exadata patches are full-stack and include necessary OS updates to maintain a certified and supported environment. The OCI console manages the application of these comprehensive patches.

B. Patching all nodes concurrently would cause a complete system outage, which contradicts the high-availability architecture of Exadata. The process is explicitly designed to be rolling.

D. The OCI console provides a unified interface for patching all major components of the Exadata service, including the database nodes' OS, not just the storage servers.

1. Oracle Cloud Infrastructure Documentation, "Update the Operating System on a Virtual Machine": "You can update the operating system of the virtual machines in a VM cluster... The update process is a rolling one, with only one virtual machine cluster node being taken offline at a time. This ensures that the cluster is continuously available during the update process." (This confirms the rolling update of the OS on database nodes to minimize downtime).

2. Oracle Cloud Infrastructure Documentation, "Updating an Exadata Cloud Infrastructure System": "You can update the database servers and the storage servers in your Exadata Cloud Infrastructure system... You can update the database servers by applying a patch to the Grid Infrastructure, and you can update the storage servers by applying a patch to the Exadata system software." (This confirms that database servers and storage servers are updated as separate operations).

3. Oracle Cloud Infrastructure Documentation, "Patch a Grid Infrastructure Deployment": "The patching process is a rolling one, with only one node being taken offline at a time." (This reinforces the rolling nature of the update process for the database nodes, which host the Grid Infrastructure).

When you provision an Oracle Cloud Infrastructure (OCI) Base Database Service on a virtual machine, the system uses OCI Block Volumes for the persistent storage of database files (such as datafiles, control files, and redo logs). These high-performance, network-attached block storage volumes are attached to the compute VM instance that hosts the database. This configuration provides durable, scalable, and reliable storage required for enterprise database workloads. While some specific VM shapes offer local NVMe storage, Block Volumes are the standard and primary storage mechanism for most VM shapes available for the Base Database Service.

B. Object Storage is the default storage option for database datafiles.

Object Storage is designed for unstructured data and is used for backups and archives due to its high latency, not for the high-performance I/O operations of active database datafiles.

C. Local NVMe storage is always the default for BaseDB.

Local NVMe storage is only available on specific high-performance "DenseIO" VM shapes. Standard VM shapes, which are commonly used, rely exclusively on remote Block Volumes for storage.

D. File Storage is mandatory for database backups.

The primary and default destination for managed database backups in the Base Database Service is OCI Object Storage, not File Storage. File Storage is not a mandatory component for backups.

1. Oracle Cloud Infrastructure Documentation, "Overview of Bare Metal and Virtual Machine DB Systems":

Under the section for Virtual Machine DB Systems, it states: "The DB system uses Oracle Cloud Infrastructure Block Volumes for database storage." This directly supports the correct answer (A) and refutes option C's claim that local storage is always the default.

Reference: Oracle Cloud Infrastructure Documentation > Databases > Base Database Service > For Administrators > Overview of Bare Metal and Virtual Machine DB Systems.

2. Oracle Cloud Infrastructure Documentation, "Backing Up a Database on a VM DB System":

This document details the backup options, stating: "The Base Database service supports two backup destinations for DB systems: Oracle Cloud Infrastructure Object Storage...and local storage on the DB system host..." This confirms Object Storage is a primary backup destination, refuting the claims in options B and D.

Reference: Oracle Cloud Infrastructure Documentation > Databases > Base Database Service > For Users > Backing Up and Restoring > Backing Up a Database on a VM DB System.

3. Oracle Cloud Infrastructure Documentation, "Storage Options for Your DB System":

This page clarifies the storage types: "Virtual machine DB systems can use Oracle Cloud Infrastructure Block Volumes storage or local NVMe storage." It further explains that Block Volumes are used for standard shapes, while local NVMe is for DenseIO shapes, invalidating the "always" in option C.

Reference: Oracle Cloud Infrastructure Documentation > Databases > Base Database Service > For Administrators > DB System Storage.

The underlying database architecture and scalability characteristics are fundamental properties of the Oracle NoSQL Database Cloud Service itself. These aspects, such as sharding for horizontal scaling, storage management, and replication for high availability, are managed by Oracle Cloud Infrastructure and are independent of the client-side application or the Software Development Kit (SDK) used to connect to it. The SDK is an interface or a client library; its primary role is to translate application code into API requests that the service understands. The choice of SDK impacts how the application is written, not how the service is architected or performs.

A. Syntax for querying data is highly dependent on the SDK. Each language (e.g., Python, Java, Go) has its own specific methods, classes, and syntax for constructing and executing queries.

B. The method for authenticating is implemented differently across SDKs. While the underlying principles (e.g., API keys, instance principals) are OCI-wide, the code to configure and use them varies by language.

D. Error handling mechanisms are specific to the programming language and its SDK. For example, Java uses try-catch blocks with specific exception classes, while Go uses an if err != nil pattern.

1. Oracle NoSQL Database Cloud Service Documentation - Overview: This document describes the service's architecture, highlighting features like "scale-out performance" and "high availability" as inherent to the service, with no mention of them being influenced by client SDKs. (See "About Oracle NoSQL Database Cloud Service" section).

2. Oracle NoSQL Database Cloud Service Documentation - Using the NoSQL SDK for Python: This guide details the Python-specific classes and methods for interacting with the service, such as NoSQLHandle, QueryRequest, and SignatureProvider, demonstrating how syntax is tied to this specific SDK. (See "Getting a Handle" and "Querying Data" sections).

3. Oracle NoSQL Database Cloud Service Documentation - Using the Oracle NoSQL SDK for Java: This document shows the Java-specific implementation for the same operations, using different class names and coding patterns (e.g., NoSQLHandleFactory, QueryRequest), which contrasts with the Python SDK and confirms that syntax, authentication, and error handling are SDK-dependent. (See "Getting a Handle" and "Working with Tables and Data" sections).

The primary benefit of using "Cloud Tooling" for Exadata Database Service is the automation of complex and time-consuming lifecycle management tasks. This tooling, provided through the Oracle Cloud Infrastructure (OCI) console and APIs, automates the initial provisioning of the entire Exadata stack. It also simplifies and automates ongoing maintenance activities such as patching the infrastructure (database servers, storage servers, network fabric), Grid Infrastructure, and Database Homes. This significantly reduces the administrative overhead and potential for human error compared to performing these tasks manually on an on-premises system.

A. Cloud services abstract the underlying hardware, offering less, not more, granular hardware control. The focus is on simplified management through predefined configurations.

C. While infrastructure management is automated, a Database Administrator is still essential for database-level tasks like performance tuning, schema management, and security.

D. Cloud services typically enforce the use of supported software versions. On-premises deployments offer more flexibility for running older, unsupported versions (at the owner's risk).

1. Oracle Cloud Infrastructure Documentation, "Overview of Exadata Database Service on Dedicated Infrastructure": This document states, "Oracle automates infrastructure maintenance tasks such as patching the Exadata database servers, storage servers, and network switches." It also highlights the simplified provisioning process, which directly supports the automation benefit. (Reference: docs.oracle.com/en-us/iaas/exadata/doc/overview.html, Section: "Exadata Database Service on Dedicated Infrastructure Components")

2. Oracle Cloud Infrastructure Documentation, "Updating an Exadata Cloud Infrastructure": This section details the automated patching capabilities provided by the cloud tooling. It describes how the service "provides a flexible patching mechanism" for both infrastructure and database software, which is a core aspect of automated lifecycle management. (Reference: docs.oracle.com/en-us/iaas/exadata/doc/exacs-patching.html, Section: "Patching an Exadata Cloud Infrastructure System")

3. Oracle Cloud Infrastructure Documentation, "Creating an Exadata Cloud VM Cluster": The process described for creating a VM cluster illustrates the automation of provisioning. The user specifies high-level parameters, and the cloud tooling handles the complex underlying configuration, a task that would be manual and extensive on-premises. (Reference: docs.oracle.com/en-us/iaas/exadata/doc/exacs-vm-cluster.html, Section: "Procedure for creating an Exadata cloud VM cluster")

Oracle NoSQL Database Cloud Service is a fully managed, serverless database. The service abstracts the underlying hardware infrastructure, including compute instances and their CPU utilization, from the user. Users manage performance by provisioning throughput (Read and Write Capacity Units) and storage. Autoscaling is triggered by the consumption of these provisioned units. Metrics like rejected (throttled) requests and operation latency are direct indicators of whether the provisioned capacity is sufficient for the workload. CPU utilization of the host instances is an internal Oracle-managed metric and is not exposed to the user or used as a basis for customer-configured autoscaling.

B. Number of rejected read requests due to insufficient RCUs.

This is a primary metric (ReadThrottleCount) indicating the provisioned read capacity is exceeded, making it highly relevant for scaling up.

C. Number of rejected write requests due to insufficient WCUs.

This is a primary metric (WriteThrottleCount) indicating the provisioned write capacity is exceeded, making it highly relevant for scaling up.

D. Latency of read and write operations.

High latency is a key performance indicator that the system is approaching its capacity limits, making it a very relevant metric for scaling decisions.

1. Oracle Cloud Infrastructure Documentation, About Oracle NoSQL Database Cloud Service: "Oracle NoSQL Database Cloud Service is a fully managed database service that handles the administration of the underlying infrastructure, including hardware and software provisioning, and scaling." This statement confirms the abstraction of hardware metrics like CPU from the user.

Source: Oracle Cloud Infrastructure Documentation, "Overview of NoSQL Database Cloud Service," section "About Oracle NoSQL Database Cloud Service."

2. Oracle Cloud Infrastructure Documentation, NoSQL Database Metrics: This document lists the available metrics for the NoSQL Database service. The list includes ReadThrottleCount, WriteThrottleCount, GetRequestLatency, and PutRequestLatency. It does not include any metric related to the CPU utilization of the underlying service infrastructure, confirming that this is not a user-facing metric for monitoring or autoscaling.

Source: Oracle Cloud Infrastructure Documentation, "Monitoring," section "NoSQL Database Metrics."

3. Oracle Cloud Infrastructure Documentation, Estimating and Monitoring Capacity: "If you exceed the provisioned throughput for a table for an extended period of time, you will experience a ThrottlingException for the excess requests." This directly links rejected requests (throttling) to exceeding provisioned capacity, establishing the relevance of options B and C.

Source: Oracle Cloud Infrastructure Documentation, "Using Oracle NoSQL Database Cloud Service," section "Estimating and Monitoring Capacity."