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

The database fleet summary page provides a unified view of your fleet of Oracle Databases in a compartment or in a Database Group on the Oracle Database fleet summary page1. You can use this page to perform the following tasks:

• View database log entries: You can view the log entries for each database in your fleet by clicking on the Logs tab. You can filter the log entries by severity, time range, and keywords. You can also download the log files for further analysis1.
• View the current database resource usage: You can view the current resource usage for each database in your fleet by clicking on the Metrics tab. You can see the metrics for CPU utilization, memory utilization, storage utilization, and I/O throughput. You can also customize the metrics dashboard by adding or removing metrics, changing the time range, and applying filters1.
• View the status of the databases: You can view the status of each database in your fleet by looking at the Status column in the table. You can see if the database is available, unavailable, or in maintenance mode. You can also see the database type, version, edition, and shape1.

The database fleet summary page does not provide the following capabilities:

• Migrate databases to OCI: You cannot migrate databases to OCI using the database fleet summary page. You need to use other tools and methods to migrate databases to OCI, such as Data Pump, RMAN, GoldenGate, or Zero Downtime Migration.
• Compare database performance metrics overtime: You cannot compare database performance metrics overtime using the database fleet summary page. You need to use the Performance Hub to compare the performance of different databases or the same database at different points in time. You can access the Performance Hub by clicking on the database name and then clicking on the Performance Hub tab.
• Execute a DDL command on the databases: You cannot execute a DDL command on the databases using the database fleet summary page. You need to use the SQL Developer Web or the SQL Worksheet to execute SQL statements on the databases. You can access the SQL Developer Web or the SQL Worksheet by clicking on the database name and then clicking on the SQL Developer Web or the SQL Worksheet tab. References: 1: Monitor the Health of Your Oracle Database Fleet - Oracle Help Center : [Migrate Databases to Oracle Cloud Infrastructure - Oracle Help Center] : [Use the Performance Hub - Oracle Help Center] : [Use SQL Developer Web - Oracle Help Center]

Learn more:

Oracle recommends that you do not stop any servers or database instances before applying a patch to your DB system. Stopping the servers or instances can cause the patching process to fail or take longer than expected. Instead, you should run the precheck operation before you apply any update to verify that your DB system meets the patching prerequisites. You should also back up your databases before you apply any updates to your system, and patch the DB system before updating a database for DB systems with Grid Infrastructure/ASM storage management. Therefore, statement D is not an Oracle best practice and the rest are. References:

• 3: In-Place Upgrade for Database Cloud Service (DBCS) VM DB Systems
• 4: Update a DB System - Oracle Help Center

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 Oracle Cloud Infrastructure (OCI) Database Management Service is a fully integrated feature of Oracle Database that provides a single console for managing and monitoring your Oracle Databases on OCI. It supports Oracle Database versions 11.2.0.4 and later, running on any edition, including Enterprise Edition, Standard Edition 2, and Express Edition1. It can monitor both OCI databases and external databases that are accessible from the OCI tenancy2. External databases are databases that are not deployed on OCI, but can be registered with the Database Management Service using a Database Management private endpoint and a Database Management agent3.

According to the documentation, the following types of external databases are supported by the Database Management Service3:

• Oracle Database on-premises
• Oracle Database on Oracle Cloud Infrastructure Classic
• Oracle Database on other cloud platforms
• Oracle Exadata Cloud@Customer
• Oracle Exadata Database Machine

Therefore, the correct answer is A and C, as they are both external databases that can be monitored by the Database Management Service. B is incorrect, because Oracle Autonomous Database is not an external database, but an OCI database that is managed by Oracle and does not require a Database Management agent4. D is incorrect, because Oracle 11gR2 Database is not a supported version for the Database Management Service, as it requires at least 11.2.0.41.

References: 1: Supported Database Versions and Features 2: About Database Management 3: Managing External Databases 4: Autonomous Database on Shared Exadata Infrastructure

You can independently scale the storage used by the VM DB System but the Available Data storage size and Recovery Area storage size cannot be decreased. This is because the VM DB System uses block volumes to store the database data files and the recovery area files, and the block volumes cannot be downsized1. However, you can increase the storage size of the block volumes at any time, either individually or together, to accommodate the growth of your database1. You can also scale the compute resources of the VM DB System independently of the storage resources, by adding or removing CPU cores or changing the shape of the VM DB System1. Scaling the storage or compute resources of the VM DB System does not affect the availability of the database, as the scaling operations are performed online1. References:

• 1: Scaling a Virtual Machine DB System - Oracle Help Center
• Independent Scaling: Oracle VM DB Systems allow you to scale the Available Data storage (the main storage for your database) and the Recovery Area storage (used for backups, Flashback logs, etc.) separately.expand_more This provides flexibility.
• No Decreasing Storage: Once provisioned or scaled up, neither the Available Data storage nor the Recovery Area storage can be scaled 

pen_spark

down.exclamation This is likely to protect data integrity.

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

To consolidate two databases into a single Oracle Home, you need to perform the following actions1:

• Schedule a downtime window with the team using the 193B database. This is necessary because you need to stop the database service and detach the pluggable databases (PDBs) from the source Oracle Home before moving them to the target Oracle Home2.
• Use the Move Database option from the console to relocate the database to the target Oracle Home. This is the easiest and fastest way to move the database and its PDBs to a different Oracle Home. You can use the Oracle Cloud Infrastructure Console or the API to initiate the move operation, which will automatically copy the required files, update the configuration, and restart the database service in the target Oracle Home3.

Therefore, statements A and D are correct, and statements B and C are incorrect. Copying the sqlnet.ora and spfile from OH193_B to OH193_A and restarting PDBs is not sufficient to move the database to a different Oracle Home, as it does not update the Oracle Inventory, the Oracle Restart configuration, or the database registry4. Creating a new container database under OH193B and migrating the PDBs from 193B to 193A is not necessary, as you can move the existing PDBs directly to the target Oracle Home without creating a new container database5. References: 1: Oracle Base Database Services 2023 Professional, Section 4.2.2: Moving a Database to a Different Oracle Home 2: Base Database Service, Section 4.2.2.1: Prerequisites for Moving a Database to a Different Oracle Home 3: Base Database Service, Section 4.2.2.2: Moving a Database to a Different Oracle Home 4: [Oracle Database Administrator’s Guide], Section 2.4.1: Moving Oracle Database to a New Oracle Home 5: [Oracle Database Administrator’s Guide], Section 19.1.1: Overview of Pluggable Database Migration

The statement that is true about rebooting a virtual machine (VM) DB system node using the Oracle Cloud Infrastructure Console is D. On the VM DB system details page, find the node that you want to reboot, click the Actions (three dots) menu for that node, and then click Reboot. This is the procedure that is described in the official documentation12. It allows you to reboot a single node of a multi-node DB system individually, which may be necessary in some cases, such as scheduled maintenance1. The node is shut down and then restarted, and the floating IP address may take some time to be updated1.

A is incorrect, because the VM DB system nodes can be rebooted individually, as explained above. B is incorrect, because the VM DB system can be rebooted from the Oracle Cloud Infrastructure Console, as well as from the REST APIs or dbcli1. C is incorrect, because this is not the correct way to reboot a VM DB system node. Stopping and starting the DB system affects all the nodes, not just one, and it also stops and starts the database instances. This is different from rebooting a node, which does not affect the database instances1.

References: 1: Reboot a DB System 2: Reboot a DB System : Stop and Start a DB System

Oracle Cloud Infrastructure (OCI) provides various methods to monitor the performance and availability of your MySQL Database Service system. You can use the following methods to collect and analyze useful quantitative data about your system1:

• Data points: A data point is a single value that represents a metric at a specific point in time. Data points are collected by the OCI Monitoring service and stored in a time series database. You can use data points to track the changes in your system over time and compare different metrics2.
• Metrics: A metric is a named set of data points that share the same namespace, dimensions, and unit of measurement. Metrics are used to measure the behavior and utilization of your system, such as connection count, statement count, latency, OCPU usage, memory usage, and disk I/O. You can use metrics to create charts and dashboards to visualize your system performance3.
• Queries: A query is a way to retrieve and manipulate data points from the time series database. You can use queries to filter, aggregate, transform, and analyze metrics data. You can also use queries to create alerts and notifications based on certain conditions or thresholds4.

Therefore, statements B, D, and E are true, and statements A and C are false. Notifications and alarms are not methods to measure data, but rather methods to notify you when certain data points meet certain criteria5. References: 1: Monitor your MySQL Database Service using MySQL Enterprise Monitor 2: [Oracle Cloud Infrastructure Documentation], Monitoring Overview 3: [Oracle Cloud Infrastructure Documentation], Metrics Overview 4: [Oracle Cloud Infrastructure Documentation], Query Language Reference 5: [Oracle Cloud Infrastructure Documentation], Alarms Overview

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

Updating a DB system on a virtual machine updates the Oracle Database software and the Grid Infrastructure software, but not the operating system. The operating system can be updated separately using the Upgrade option in the Console or the API. Therefore, statement D is false and the rest are true. References:

• 3: Update a DB System - Oracle Help Center
• 4: Upgrade a DB System - Oracle Help Center

To manage an external database using the Oracle Cloud Infrastructure Database Management Service, you must create or configure a database handle and a database connection1. A database handle is a resource that represents an external database in Oracle Cloud Infrastructure2. It contains information such as the database name, version, edition, and deployment type. A database connection is a resource that enables you to connect a database handle to an Oracle Database instance located outside of Oracle Cloud Infrastructure3. It contains information such as the host name, port number, service name, and credentials. You can create and manage database handles and connections using the Oracle Cloud Infrastructure Console or the REST API23.

A is incorrect, because a dynamic group is not required to manage an external database. A dynamic group is a group of Oracle Cloud Infrastructure resources that are dynamically matched according to rules that you define4. You can use a dynamic group to grant permissions to the Database Management agent, which is a software component that runs on the host where the external database is located and communicates with the Database Management service5. However, creating a dynamic group is not mandatory, as you can also use other methods to grant permissions to the agent, such as using a user API key or an instance principal5.

C is incorrect, because a database group is not required to manage an external database. A database group is a logical grouping of databases that you can use to perform actions on multiple databases at once. You can create a database group for external databases, but it is not a prerequisite for managing them.

References: 1: About Database Management 2: Manage the Handles for External Database 3: Manage the Connections for External Database 4: Managing Dynamic Groups 5: About Database Management Agent : Managing Database Groups

Oracle Exadata Database Service has specific network requirements for the backup subnet.expand_more Here's the calculation:

• IPs per Database Compute Server: Each server requires 3 IP addresses on the backup subnet.expand_more
• Additional Reserved IPs: The Networking service within Exadata reserves 3 IP addresses in the backup subnet.expand_more
• Total Calculation:

References:

• Oracle Exadata Cloud Service (ExaCS) - Network Setup: https://docs.oracle.com/en-us/iaas/exadatacloud/exacs/ecs-network-setup.html

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]

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

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