Oracle 1z0-1093-23 Oracle Base Database Services 2023 Professional Exam Practice Test

The method that you must use to patch databases on Exadata Database Service with the least amount of downtime is to create a Data Guard standby and execute standby first patching. This method involves creating a physical standby database on a different Exadata system with the same configuration as the primary database, and then applying the patch to the standby database first. After verifying that the patch is applied successfully and the standby database is in sync with the primary database, you can perform a switchover to make the standby database the new primary database. This way, you can minimize the downtime of the primary database and ensure a smooth patching process1. You can use the Oracle Data Guard Broker or the dbaascli utility to create and manage the Data Guard configuration2.

The other options are not the best methods to patch databases on Exadata Database Service with the least amount of downtime because:

• A. Conduct in place patching of the database Home: This method involves applying the patch directly to the database home of the primary database. This method requires you to shut down the database and restart it after the patching, which can cause a significant downtime and potential data loss1.
• B. Leverage Patchmgr to execute patching the database Home: This method involves using the patchmgr tool to patch the database home of the primary database. This method also requires you to shut down the database and restart it after the patching, which can cause a significant downtime and potential data loss1. The patchmgr tool is mainly used for patching the operating system of the Exadata compute nodes, not the database home3.
• D. Leverage Opatch to execute patching the database Home: This method involves using the opatch tool to patch the database home of the primary database. This method also requires you to shut down the database and restart it after the patching, which can cause a significant downtime and potential data loss1. The opatch tool is mainly used for applying one-off patches, not the quarterly patch updates4.
• E. Move the database to a new Home with the desired patch level: This method involves creating a new database home with the desired patch level and then moving the database to the new home. This method can reduce the downtime compared to the in-place patching methods, but it still requires you to stop and start the database during the move operation1. This method also consumes more storage space and requires more steps to complete1.

References: 1: Patching Exadata Cloud Service 2: Using Oracle Data Guard on Exadata Cloud Service 3: Updating Guest VM Operating System 4: Patching Oracle Database and Oracle Grid Infrastructure Software Manually 5: Patching Exadata Cloud Service 6: Using Oracle Data Guard on Exadata Cloud Service 7: Patching Oracle Database and Oracle Grid Infrastructure Software Manually

The NoSQLHandle interface is used to access Oracle NoSQL tables and perform various operations on them, such as getting, putting, deleting, querying, and indexing rows. However, it is not used to set the row retention time, which is a property of the table itself. The row retention time is specified when creating or altering a table using the TableRequest class, which is a subclass of Request. The NoSQLHandle interface does not have a method to create or alter tables, only to execute requests that are already created by the application12. References:

• NoSQLHandle (Oracle NoSQL Database Java API)
• Obtaining a NoSQL handle - Oracle Help Center

 A VM DB system database uses OCI block storage instead of local storage. You specify a storage size when you create the DB system, and you can scale up the storage as required at any time1. Scaling the storage does not affect the availability or performance of the database2. You can use the Oracle Cloud Infrastructure Console or the API to scale the storage of a VM DB system1.

The other options are incorrect because:

• A. After you have provisioned a VM DB system, you cannot increase or decrease block storage. This is false because you can increase or decrease the storage of a VM DB system at any time1.
• C. If you want to increase or decrease the storage, you must change the shape of the VM DB system. This is false because changing the shape of a VM DB system affects the number of CPU cores, not the storage3. You can scale the storage independently of the shape1.
• D. If a VM DB system has different requirements for block storage, you can increase or decrease the storage at any time without impacting the system. This is partially true, but not the best answer. You can increase or decrease the storage at any time, but there is a limitation if you are scaling from a value less than 10,240 GB (10 TB) to a value exceeding 10,240 GB. In that case, you must perform the scaling in two operations2.

References: 1: Scale the DB System 2: About Virtual Machine DB Systems 3: [Change the Shape of a DB System]

The action that causes an error when creating a MySQL DB system is using the username “mysql.sys”. This is because “mysql.sys” is a reserved username for the MySQL system schema, which contains views and stored procedures that implement server functionality1. You cannot create a user with the same name as the system schema, as it would cause conflicts and errors1. You should choose a different username for the administrator of the MySQL DB system, such as “mysql.admin” or “mysql.user”.

The other actions do not cause errors, but they may have some implications:

• Storage size of 50 GB is not too small, but it may not be enough for your database workload and growth. You can choose a storage size from 50 GB to 16 TB when creating a MySQL DB system2. You can also scale up the storage size later if needed2.
• Host name of “mysql-host” is valid, but it should be unique within the subnet where the DB system is deployed2. You can use letters, numbers, and hyphens in the host name, but it must start and end with a letter or a number2.
• Maintenance Window start day and time is not required, but it is recommended to specify a preferred time for applying maintenance updates to the DB system2. If you do not specify a Maintenance Window, Oracle will assign a random day and time for the maintenance updates2.

References:

• MySQL :: MySQL 8.0 Reference Manual :: 5.6 The mysql System Schema
• MySQL :: MySQL Database Service User Guide :: 3.1 Creating a MySQL DB System

To use the MySQL Database Service, you need to have the following three prerequisites1:

• You must create a tenancy and be able to sign in to it. A tenancy is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources2. You need to have a valid Oracle Cloud account and credentials to access your tenancy and use the MySQL Database Service.
• You must create a compartment to store your resources. A compartment is a logical container that you can use to organize and isolate your cloud resources within a tenancy3. You can create one or more compartments to store your MySQL Database Service resources, such as MySQL DB systems, backups, and connections. You can also control the access and permissions for each compartment using policies4.
• You or your group must be granted the policies described in Mandatory Policies. Policies are documents that specify who can access which resources, and how5. To use the MySQL Database Service, you need to have the necessary permissions to create and manage the MySQL Database Service resources, as well as the related Oracle Cloud Infrastructure resources, such as Virtual Cloud Networks, subnets, and security lists. The documentation provides a list of mandatory policies that you or your group must be granted to use the MySQL Database Service.

D is incorrect, because you do not have to download the latest MySQL version from https://edelivery.oracle.com/. The MySQL Database Service is a fully managed service that provides you with the MySQL version that you select when creating a MySQL DB system. You do not have to download or install any MySQL software on Oracle Cloud Infrastructure.

E is incorrect, because you do not have to install the downloaded MySQL version onto Oracle Cloud Infrastructure. As mentioned above, the MySQL Database Service is a fully managed service that handles the installation and configuration of the MySQL software for you.

References: 1: Getting Started With MySQL Database Service 2: About Your Tenancy 3: About Compartments 4: Managing Compartments 5: About Policies : Mandatory Policies : Creating a MySQL DB System

The exacli tool is a command-line interface that can be used to monitor and manage the storage servers in Exadata Database Service. The exacli tool provides access to the cellcli command, which is used to manage and monitor individual Oracle Exadata storage cells1. The exacli tool can also perform other tasks, such as checking the status of the storage server grid, viewing the configuration and performance metrics of the storage servers, and applying patches and updates to the storage servers2.

The other options are not tools that can be used to monitor a storage server in Exadata Database Service. The dbaascli tool is a command-line interface that can be used to perform various administrative tasks on the database servers, such as creating and deleting databases, managing backups and restores, and applying patches and updates3. The OCI CLI tool is a command-line interface that can be used to interact with Oracle Cloud Infrastructure services, such as creating and managing resources, configuring network and security settings, and accessing the Console4. The ocpucli tool is not a valid tool name, but it may be confused with the opctli tool, which is a command-line interface that can be used to manage Oracle Private Cloud Appliance, a converged infrastructure system that is not related to Exadata Database Service5. References:

• exacli Command-Line Interface - Oracle Help Center
• Monitor Oracle Exadata Storage Infrastructure in OCI Database Management
• dbaascli Utility Reference - Oracle Help Center
• Command Line Interface (CLI) - Oracle Help Center
• Oracle® Private Cloud Appliance Administrator’s Guide

Exadata Cloud@Customer is a cloud service that delivers the full power of the Exadata platform in your data center. You can create VM clusters on Exadata Cloud@Customer to run Oracle Database instances on virtual machines. You can scale up and down the following resources on your VM cluster1:

• CPU: You can increase or decrease the number of CPU cores allocated to each database node in the VM cluster. You can also enable or disable auto-scaling, which allows the system to automatically adjust the CPU cores based on the workload demand2.
• Memory: You can increase or decrease the amount of memory allocated to each database node in the VM cluster. You can also enable or disable auto-scaling, which allows the system to automatically adjust the memory based on the workload demand2.
• Local Storage: You can increase or decrease the size of the local storage allocated to each database node in the VM cluster. Local storage is used for the operating system, software installation, and temporary files. You can also enable or disable auto-scaling, which allows the system to automatically adjust the local storage based on the workload demand2.
• Exadata Storage: You can increase or decrease the size of the Exadata storage allocated to the VM cluster. Exadata storage is used for the database files, such as data files, control files, redo logs, etc. You can also enable or disable auto-scaling, which allows the system to automatically adjust the Exadata storage based on the workload demand2.

Therefore, statement E is correct, and statements A, B, C, and D are incorrect. Persistent Memory (PMEM), Flash Storage, Network, and Grid Infrastructure Bandwidth are not resources that can be scaled up and down on your VM cluster on Exadata Cloud@Customer1. References: 1: Exadata Cloud@Customer 2: Exadata Cloud@Customer’s distributed cloud database platform

The characteristic that is NOT a factor that impacts the capacity units for provisioning a NoSQL Database Cloud Service table is the query pattern. The query pattern refers to the frequency and complexity of the queries that are executed on the table. The query pattern does not affect the capacity units, which are based on the write and read throughput and the storage capacity of the table1.

The other options are factors that impact the capacity units for provisioning a NoSQL Database Cloud Service table because:

• A. Record size: The record size affects the write and read units, which are defined as the throughput of up to 1 KB of data per second for a write or read operation. If the record size is larger than 1 KB, then more write or read units are required to achieve the same throughput1.
• B. Durability level: The durability level affects the read units, which are defined as the throughput of up to 1 KB of data per second for an eventual consistent read operation. If the durability level is set to absolute consistent, which guarantees that the data returned is the most recent, then twice as many read units are required to achieve the same throughput1.
• C. Data model: The data model affects the storage capacity, which is defined as the amount of storage space used by the table. The data model determines the number and type of fields in each record, which in turn affects the storage size of each record. The more fields and complex data types in the record, the more storage capacity is required1.

References: 1: Oracle NoSQL Database Cloud Service Capacity Planning

The three strategies to migrate Oracle Database to Oracle Cloud Infrastructure (OCI) are:

• Zero Downtime Migration: This is a tool that provides a simplified and automated migration experience, providing zero to negligible downtime for the production system. It supports migrating Oracle Database versions 11.2.0.4 and later, running on any platform, to any OCI Database service, including Exadata, Cloud@Customer, and Autonomous1.
• Migration Workbench: This is a feature of Oracle Enterprise Manager that provides a user interface to perform database migrations using various methods, such as Data Pump, Transportable Tablespaces, or Cross-Platform Transportable PDBs. It supports migrating Oracle Database versions 11.2.0.4 and later, running on any platform, to any OCI Database service, including Exadata, Cloud@Customer, and Autonomous2.
• GoldenGate: This is a software product that enables data replication and integration across heterogeneous databases and platforms. It supports migrating Oracle Database versions 10.2 and later, running on any platform, to any OCI Database service, including Exadata, Cloud@Customer, and Autonomous. It also supports bi-directional replication and zero downtime upgrades3.

B is incorrect, because autonomous migration is not a strategy to migrate Oracle Database to OCI, but a feature of Oracle Autonomous Database that allows you to migrate data from other sources, such as Oracle Database, MySQL, MongoDB, or Amazon S3, to an Autonomous Database instance using Oracle Data Pump or SQL Developer Web4.

C is incorrect, because Real Application Clusters (RAC) is not a strategy to migrate Oracle Database to OCI, but a feature of Oracle Database that provides high availability and scalability by enabling multiple instances to access the same database across a cluster of servers5.

References: 1: Get started with Zero Downtime Migration 2: Migrate Oracle Databases to OCI 3: Oracle GoldenGate 4: Migrate Data to Autonomous Database 5: Oracle Real Application Clusters (RAC)

Exadata Snapshots are a feature of the Exadata Database Service that allows you to create space-efficient read-only or read-write clones of an existing database1. Exadata Snapshots use the Exadata SPARSE disk group to store the sparse files that contain the data that is read and written by the snapshots2. The sparse files only store the changed blocks, not the entire data, which saves space and improves performance2. Multiple users can create independent Exadata Snapshots from the same test master, which is a full read-only clone of the source database3. The test master can be created from a backup of the source database or from a Data Guard standby database3. Before creating Exadata Snapshots from the test master, you can modify the data in the test master, if required.

Therefore, the correct answer is A, C, and D. B is incorrect, because Exadata Snapshots can utilize all the Exadata features, such as Smart Scan, Smart Flash Cache, Hybrid Columnar Compression, and so on. E is incorrect, because you cannot modify the data in the test master after creating Exadata Snapshots from it, as it becomes read-only.

References: 1: About Exadata Snapshots 2: Sparse Disk Sizing and Allocation Methodology 3: Creating Exadata Snapshot Masters : Refresh Considerations, or Lifecycle of Exadata Snapshots : Exadata Snapshots

• Core Exadata Setup: When provisioning an Exadata Cloud Infrastructure resource, you must specify:
• VCN Creation: The system automatically sets up a default Virtual Cloud Network (VCN) and subnet to handle Exadata network traffic.

pen_spark

A Service Gateway is a virtual router that enables private access to multiple Oracle services in the Oracle Services Network, a conceptual network that is reserved for Oracle services and composed of a list of regional CIDR blocks1. A Service Gateway can be used to access Object Storage, which is one of the Oracle services supported by the Service Gateway2. A Service Gateway can only connect to services in the same region of its VCN, not in other regions3. A Service Gateway cannot be used to connect to the Internet, as it does not have a public IP address4. A Service Gateway can be used with either a private or a public subnet, as long as the subnet has a route table that directs traffic to the Service Gateway5. References: 1: Service Gateway | Oracle 2: [Oracle Cloud Infrastructure Documentation] 3: [Oracle Cloud Infrastructure Documentation] 4: [Oracle Cloud Infrastructure Documentation] 5: [Oracle Cloud Infrastructure Documentation]

v When you use the “Stop” option from the Console of an Exadata Database Service virtual machine within a VM cluster, the following two statements are true1:

• Billing for the CPU stops but billing for the Exadata Infrastructure continues. This is because the “Stop” option only stops the virtual machine (VM) and releases the OCPU resources allocated to it, but does not terminate the VM or delete the associated block volumes1. Therefore, you are not charged for the OCPU usage of the stopped VM, but you are still charged for the Exadata Infrastructure and the block volume storage1. You can resume the billing for the OCPU by restarting the VM from the Console1.
• The stopped VM is not available to any other database deployment. This is because the “Stop” option only stops the VM and does not delete it or detach it from the VM cluster1. Therefore, the stopped VM remains associated with the original database deployment and cannot be used by any other database deployment1. You can make the VM available again by restarting it from the Console1.

The other statements are false because1:

• The “Stop” option only stops the selected VM and does not affect the other VMs in the cluster. You can stop or start individual VMs in the cluster as needed, without impacting the availability of the other VMs1.
• The “Stop” option only stops the databases running on the selected VM and does not affect the databases running on the other VMs in the cluster. You can stop or start individual databases in the cluster as needed, without impacting the availability of the other databases1.
• The “Stop” option does not stop the billing for the OCPU and Infrastructure until the VM restarts. As explained above, the “Stop” option only stops the billing for the OCPU, but not for the Infrastructure or the block volume storage. The billing for the OCPU resumes when the VM restarts1. References:
• 4: Manage VM Clusters - Oracle Help Center

Oracle Enterprise Manager and Service Console are two tools that can be used to monitor Exadata Database Service. Oracle Enterprise Manager is a comprehensive management solution that provides a single interface for monitoring and managing all Exadata, ExaDB-D and ExaDB-C@C systems, along with any other targets1. Oracle Enterprise Manager enables you to visualize storage and compute data, view performance metrics of your Exadata components, and perform administrative tasks such as patching, backup, and recovery1. Service Console is a web-based user interface that allows you to monitor and manage your Exadata Cloud Service instances2. Service Console provides information about the status, configuration, and utilization of your Exadata systems, and enables you to perform operations such as scaling, patching, backup, and restore2.

The other options are not valid tools for monitoring Exadata Database Service because:

• B. Oracle Management Cloud is a suite of cloud services that provides integrated monitoring, management, and analytics for applications, databases, middleware, and infrastructure3. Oracle Management Cloud is not specific to Exadata Database Service, and does not provide the same level of functionality and integration as Oracle Enterprise Manager4.
• C. Oracle Cloud Monitor is not a real tool, but a fictitious name. There is no such tool as Oracle Cloud Monitor in Oracle Cloud Infrastructure or Oracle Cloud Services.
• D. Oracle Internet Monitoring Suite (IMS) is also not a real tool, but a fictitious name. There is no such tool as Oracle Internet Monitoring Suite in Oracle Cloud Infrastructure or Oracle Cloud Services.

The users created on Database Servers that can be used for both Oracle database and host management of your Exadata Database Service are the root, opc, oracle, and grid users1. These users have different roles and privileges as follows:

• root: The root user is the superuser on the Database Servers. The root user can perform any administrative task on the host, such as installing software, configuring the network, and managing the file system. The root user can also access the Oracle Database as the SYSDBA user1.
• opc: The opc user is the default user that you use to connect to the Database Servers using SSH. The opc user has sudo privileges to run commands as root or other users. The opc user can also access the Oracle Database as the SYSDBA user1.
• oracle: The oracle user is the owner of the Oracle Database software and the Oracle Database home directory. The oracle user can perform database administration tasks, such as creating and managing databases, tablespaces, and users. The oracle user can also access the Oracle Database as the SYSDBA user1.
• grid: The grid user is the owner of the Oracle Grid Infrastructure software and the Oracle Automatic Storage Management (ASM) home directory. The grid user can perform ASM administration tasks, such as creating and managing disk groups, volumes, and files. The grid user can also access the Oracle Database as the SYSASM user1.

The other options are incorrect because:

• B. root, opc, oracle, grid, and cloud users: The cloud user is not a valid user on the Database Servers. The cloud user is a user that you create in the Oracle Cloud Infrastructure Identity and Access Management (IAM) service to access the Oracle Cloud resources. The cloud user cannot access the Oracle Database or the host management of the Exadata Database Service2.
• C. opc, oracle, and grid users: This option is missing the root user, which is a valid user on the Database Servers that can access the Oracle Database and the host management of the Exadata Database Service1.
• D. root, oracle, and grid users: This option is missing the opc user, which is the default user on the Database Servers that can access the Oracle Database and the host management of the Exadata Database Service1.

References: 1: Users on Database Servers 2: Users and Roles in Oracle Cloud Infrastructure

 The recommended subnet configurations for Exadata Database Service are to use regional subnets for both client and backup, or to use a private subnet for client and a private subnet for backup12. Regional subnets span all availability domains in the region, which provides high availability and flexibility for the Exadata Database Service1. Private subnets are isolated from the internet and provide more security and control for the Exadata Database Service1. Using a public subnet for client or backup exposes the Exadata Database Service to the internet, which is not recommended1. Using a service subnet for backup is not supported, as service subnets are reserved for Oracle Cloud Infrastructure services3. References:

• Network Setup for Exadata Cloud Infrastructure Instances
• Service Gateway
• Oracle Exadata Cloud Service (ExaCS) Networking