1z0-1093-23 Practice Exam Questions with Answers Oracle Base Database Services 2023 Professional Certification

 To perform actions on a NoSQL table, such as creating, updating, deleting, or querying rows, you need to have the appropriate permissions granted by an IAM policy. The permissions are defined by the combination of the verb and the resource type. For example, the NOSQL_TABLE_WRITE permission allows you to create or update a table, and the NOSQL_ROWS_INSERT permission allows you to insert rows into a table1.

The other options are not correct permissions to perform actions on a NoSQL table. The NOSQL_ROWS_READ and NOSQL_ROWS_DELETE permissions only allow you to read or delete rows from a table, but not to insert or update them1. The NOSQL_TABLE_INSPECT and NOSQL_TABLE_UPDATE permissions only allow you to list or modify the properties of a table, but not to create or delete it1. The NOSQL_TABLE_DESTROY and NOSQL_TABLE_ALTER permissions only allow you to drop or alter a table, but not to create or update it1. References:

• Oracle NoSQL Database Cloud Service Policies Reference

Oracle database with Object Storage in Oracle Cloud Infrastructure (OCI) can be used for the following use cases:

• Database backups: Oracle Recovery Manager (RMAN) is an Oracle Database client that performs Oracle database backup and recovery. It automates the administration of Oracle backup strategies and greatly simplifies backing up, restoring, and recovering database files. RMAN can use OCI Object Storage as a backup destination, which offers reliable and cost-efficient data durability1.
• Database log files: Oracle Database can use OCI Object Storage as a destination for archiving redo log files, which are generated during normal database operation and contain a record of the changes made to the database. Archiving redo log files to OCI Object Storage can help reduce the storage costs and improve the availability and disaster recovery of the database2.

The other two options are not valid use cases for Oracle database with Object Storage in OCI:

• Database data files: Oracle Database cannot use OCI Object Storage as a storage option for data files, which store the actual data of the database. Data files require block storage, which provides low latency and high performance. OCI Object Storage is an object storage service, which provides high scalability and durability, but not low latency and high performance3.
• Database binaries: Oracle Database cannot use OCI Object Storage as a storage option for database binaries, which are the executable files and libraries that make up the Oracle Database software. Database binaries require a file system, which provides a hierarchical structure and metadata for files and directories. OCI Object Storage is an object storage service, which provides a flat namespace and metadata for objects3.

References: 1: Backing Up to Object Storage 2: Archiving Redo Log Files to Object Storage 3: Object Storage Overview

The statement that both X8M and X8 Exadata System models use InfiniBand for their internal network fabric is false. X8 uses InfiniBand for its internal network fabric whereas X8M uses RoCE (Remote Direct Memory Access over Converged Ethernet)12. RoCE is a faster and more efficient network fabric that reduces latency and increases throughput2. X8M also uses Persistent Memory (PMEM) as an additional tier of storage, which boosts performance by allowing direct access to data in memory123. X8M has more total OCPUs available than an equivalent X8 configuration because it supports more database servers and storage servers per rack13. References:

• Overview of X8M and X9M Scalable Exadata Infrastructure
• Exadata X8 vs X8M — oracle-mosc - Oracle Community
• Exadata Cloud@Customer X8M: The Best “In Datacenter” Database Cloud Platform
• Exadata Cloud Service X8M—No Database Workload is Too Large
• Oracle Exadata Database Service on Exadata Cloud@Customer X8M

The statement that is false related to loading a table into HeatWave is that data is distributed among analytics nodes by slicing tables vertically. This is false, because HeatWave distributes data among analytics nodes by slicing tables horizontally, not vertically1. Horizontal slicing means that each analytics node stores a subset of the table rows, while vertical slicing means that each analytics node stores a subset of the table columns1. Horizontal slicing enables parallel processing of queries across analytics nodes, while vertical slicing would require data shuffling and communication between analytics nodes1.

The statements that are true related to loading a table into HeatWave are:

• Data is read from InnoDB using batched, multi-threaded reads. This is true, because HeatWave loads data with batched, multi-threaded reads from InnoDB, which improves the performance and efficiency of the data loading process2.
• Data is partitioned by primary key unless data placement keys are defined. This is true, because HeatWave partitions data by the table primary key, which determines how the table rows are distributed among analytics nodes1. However, you can also define data placement keys for a table, which override the primary key and enable you to control the data distribution based on your query patterns.
• Data is converted into columnar format and sent over the network. This is true, because HeatWave converts the data into columnar format, which optimizes the data for analytical queries and reduces the storage footprint1. HeatWave then sends the data over the network to distribute it among analytics nodes in horizontal slices2.

References:

• MySQL :: MySQL HeatWave User Guide :: 2.1 HeatWave Architecture
• MySQL :: MySQL HeatWave User Guide :: 2.2 Loading Data
• [MySQL :: MySQL HeatWave User Guide :: 2.7.2 Defining Data Placement Keys]

The detail that the shape selection provides to HeatWave is the number of CPUs for the Analytic cluster. This is because the shape determines the amount of CPU and memory resources allocated to each HeatWave node, which affects the performance and scalability of the HeatWave cluster1. The shape also determines the pricing of the HeatWave cluster, as the cost is based on the number of OCPUs used by the HeatWave nodes1. The shape does not provide any information about the associated database system network, the disk partition count, or the private IP address for the HeatWave cluster, as these are not related to the shape selection1. Therefore, the correct answer is D. References:

• 5: Overview of HeatWave - Oracle Help Center

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

 To connect to the NoSQL Database Cloud Service, you need to provide the following information1:

• Signing key fingerprint: This is a unique identifier for your API signing key, which is used to authenticate your requests to the service. You can find your signing key fingerprint in the Console under Identity > Users > User Details > API Keys2.
• API signing key: This is a private key that you generate and upload to the service. You use this key to sign your requests to the service. You can create and upload an API signing key using the Console or the CLI2.
• Tenancy OCID: This is the Oracle-assigned unique ID of your tenancy. You can find your tenancy OCID in the Console under Administration > Tenancy Details > Tenancy Information3.

The other options are not required to connect to the NoSQL Database Cloud Service. A passphrase is used to encrypt your private key, but it is not needed to connect to the service. A handshake key is used to establish a secure connection between two parties, but it is not used by the NoSQL Database Cloud Service. A user ID is a unique identifier for your user account, but it is not used to authenticate your requests to the service. A component ID is a unique identifier for a specific component of the service, such as a table or an index, but it is not needed to connect to the service. An admin ID is a user account that has administrative privileges on the service, but it is not used to authenticate your requests to the service. References:

• Connect to the Service - Oracle Help Center
• Required Keys and OCIDs - Oracle Help Center
• Managing Your Tenancy - Oracle Help Center

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

 The next step to create a MySQL Database Service system is to create the MySQL DB system. This is the main resource that represents a MySQL database in Oracle Cloud Infrastructure1. To create a MySQL DB system, you need to provide some basic information, such as the name, shape, version, and credentials of the database. You also need to select the compartment, availability domain, and subnet where the MySQL DB system will be deployed2. You can create a MySQL DB system using the Oracle Cloud Infrastructure Console, the REST API, or the CLI2.

B is incorrect, because connecting to the MySQL Database Service system endpoint is not the next step, but a subsequent step after creating the MySQL DB system. You need to have a MySQL DB system up and running before you can connect to it using a MySQL client or application3.

C is incorrect, because creating a Linux compute instance is not required to create a MySQL Database Service system. A Linux compute instance is an optional resource that you can use to access your MySQL DB system from a public subnet, as MySQL DB systems are deployed in private subnets by default4. However, you can create a Linux compute instance after creating the MySQL DB system, not before.

D is incorrect, because creating a Virtual Cloud Network by using the VCN Wizard is not the next step, but a prerequisite step before creating the MySQL DB system. You need to have a VCN with a private subnet and a security list configured to allow traffic to and from the MySQL DB system5. The question states that all policies have been configured and tested, which implies that the VCN has already been created.

References: 1: About MySQL Database Service 2: Creating a MySQL DB System 3: Connecting to a MySQL DB System 4: Accessing a MySQL DB System from a Public Subnet 5: Creating a Virtual Cloud Network

To check if cloud tools are up-to-date in Exadata Database Service, you need to perform the following two steps1:

• You must first connect to Exadata Cloud Service as opc and sudo to the root user. This is because the cloud tools are installed and updated by the root user on the database servers1. The opc user is the default administrative user that has sudo privileges to run commands as root1. The oracle user is the default database user that owns the Oracle software and the database files, but it does not have access to the cloud tools1.
• Run the rpm -qa|grep -i dbaastools_exadata command. This command will list the installed packages that match the dbaastools_exadata pattern, which is the name of the cloud tooling package for Exadata Database Service1. The output will show the current version of the cloud tooling package, such as dbaastools_exadata-20.4.1-1.el7.x86_641. You can compare this version with the latest version available from the Oracle Base Database Service documentation1.

The other option, running the dbaascli patch tools list command, is incorrect because it is not a valid command for Exadata Database Service. The dbaascli utility is a command-line interface that provides various functions for managing the database service, such as patching, backup, recovery, and encryption1. However, the patch tools subcommand is not supported for Exadata Database Service, as the cloud tools are automatically updated by Oracle1. Therefore, the correct answer is C and D. References:

• 4: About Oracle Base Database Service - Oracle Help Center

You can fast provision a virtual machine (VM) database (DB) system, using Logical Volume Manager (LVM) for storage management, only for Oracle Database versions 12.2 and greater1. This is because LVM is a new feature introduced in Oracle Base Database Service to enable faster provisioning of single-node VM DB systems1. LVM allows you to create logical volumes from physical disks and manage them more easily and efficiently1. LVM also reduces the storage overhead and improves the performance of the VM DB system1. LVM is not available for Oracle Database versions lower than 12.2, or for multi-node VM DB systems, or for bare metal DB systems1. For these cases, you must use Automatic Storage Management (ASM) for storage management, which is the default and recommended option for Oracle Base Database Service1. ASM provides high availability, scalability, and performance for Oracle databases by managing the disk groups and data files1. Therefore, the correct answer is B. References:

• 3: About Oracle Base Database Service - Oracle Help Center