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

When enabling Data Guard on Exadata Database Service, the following two statements are true:

• You should use similar configurations for your Primary and Standby databases to ensure you meet the same performance service level after a role transition. This is a best practice recommended by the Oracle Maximum Availability Architecture (MAA) to avoid any performance degradation or unexpected behavior when switching roles between the primary and standby databases1. Similar configurations include the same database version, edition, shape, storage, and network settings2.
• You can enable Data Guard to support your Standby or Disaster Recovery (DR) needs with a single API call or mouse click in the Ul using cloud automation. This is one of the benefits of using Data Guard on Exadata Database Service, as it simplifies the creation and management of the standby database. You can use the Oracle Cloud Infrastructure Console, the REST API, or the CLI to enable Data Guard when creating a new database or to add Data Guard to an existing database3.

C is incorrect, because Active Data Guard does not provide read/write functionality on the standby or disaster recovery system, but read-only functionality. Active Data Guard allows you to open the standby database for read-only access while it is synchronized with the primary database, enabling real-time query and reporting on the standby database4.

D is incorrect, because you do not have to configure Data Guard manually to create the standby or DR instance for your primary Exadata Database. As mentioned above, you can use cloud automation to enable Data Guard with a single API call or mouse click in the UI3.

E is incorrect, because you can edit your configuration to change between synchronous or asynchronous transport of data to the DR site, after enabling Data Guard. You can use the Oracle Cloud Infrastructure Console, the REST API, or the CLI to modify the Data Guard association and change the protection mode, which determines the data transport method5.

References: 1: Disaster Recovery Best Practices for Exadata Database Machine using Oracle Data Guard 2: About Configuring Oracle Data Guard for Oracle Exadata Database Service on Dedicated Infrastructure 3: Using Oracle Data Guard in Exadata Cloud Service 4: About Oracle Active Data Guard 5: Modifying a Data Guard Association

To change the backup window start time for a MySQL Database Service system, you need to select Backup Window from the Edit MySQL DB System Details page and set the start time to 4 AM. This option allows you to specify the time range during which automatic backups are performed. You can also enable or disable automatic backups from this page. The other options are incorrect because they do not apply to MySQL Database Service systems. The mysqlbackup command is a tool for backing up and restoring MySQL databases, but it is not used to configure the backup window for MySQL Database Service systems. The OCI MySQL DB System Details page does not have an option to specify the backup window start time or to enable automatic backups. The Enable Automatic Backups time is not a valid setting for MySQL Database Service systems. References:

• 3: About Oracle Base Database Service - Oracle Help Center
• 4: Back Up and Recovery in Base Database Service - Oracle Help Center
• 5: About Oracle Base Database Service - Oracle Help Center

• Security Lists in OCI: Security Lists act as virtual firewalls for instances within a Virtual Cloud Network (VCN). They define a set of rules for controlling network traffic at the subnet level.
• Incorrect Statements:

References:

• OCI Security Lists: https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/securitylists.htm

 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 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

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 statements that are true about cloning a Virtual Machine DB System are:

• When creating a clone of the Virtual Machine DB system, you need to specify a new SSH key and admin password1. This is because the clone is a new DB system that requires its own credentials for security and access purposes1.
• Cloning creates a copy of a source Virtual Machine DB system as it exists at the time of the cloning operation, including the storage configuration software and database volumes12. This means that the clone will have the same database software, patches, configuration, and data as the source DB system at the time of cloning12.

The statements that are false about cloning a Virtual Machine DB System are:

• When creating a clone, you must use the same SSH key and admin password as the source Virtual Machine DB system. This is false, as explained above, you need to specify a new SSH key and admin password for the clone1.
• Cloning only creates a copy of a source Virtual Machine DB system as it exists at the time of the cloning operation, but does not include the storage configuration software and database volumes. This is false, as explained above, cloning includes the storage configuration software and database volumes of the source DB system12.

References:

• Clone a DB System
• Virtual machine DB system cloning available for single-node systems using LVM storage management

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 correct way to take an On-Demand backup of the database on Exadata Database Service on Dedicated Infrastructure in the public cloud is to use the Create Backup button in the backup section of the Database Details page1. This will create a full backup of the database and store it in the backup destination that you have configured for the database1. You can use this option to take an On-Demand backup at any time, regardless of the automatic backup schedule that you have set up1.

The other options are incorrect because:

• Connecting to Exadata Database Service as oracle user first and then taking an On-Demand backup is not supported. You cannot use the dbaascli utility or the RMAN commands to initiate an On-Demand backup on Exadata Database Service on Dedicated Infrastructure2. You can only use the Console or the API to create an On-Demand backup1.
• Disabling Automatic backup and then taking an On-Demand backup is not necessary. You can take an On-Demand backup without disabling the Automatic backup feature1. Disabling Automatic backup will stop the regular backups of the database, which is not recommended for data protection and recovery1.
• On-Demand backups are allowed on Exadata Database Service, as explained above. They are not restricted by the Automatic backup feature, which is also available and recommended for Exadata Database Service1.

References:

• Managing Database Backup and Recovery on Oracle Exadata Database Service on Dedicated Infrastructure
• Exadata Database Service on Dedicated Infrastructure

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