Oracle 1z0-902 Oracle Exadata Database Machine X9M Implementation Essentials Exam Practice Test

The CELLCLI CALIBRATE command can be used to check the health of all flash cards in the storage server, and it should be run after logging in as the celladmin user. The hardware monitoring using the storage server ILOM should also be used to check for errors and other potential issues with the flash cards. The CELLCLI list LUN DETAIL command should not be used to identify a damaged or failing flash card, since it will not provide any information about the health of the flash card.

The correct order of steps is 10, 8, 9, 11. The 10th step is to use the drop down to add Exadata X9M Database Servers, the 8th step is to use the drop down to add Exadata X9M EF Storage Servers, the 9th step is to use "Add Equipment" to add the ZFS Storage Controllers, and the 11th step is to use "Add Equipment" to add the ZFS Storage Trays. These steps are referenced in the Oracle Exadata Database Machine X9M Implementation Essentials Official Textbook, which is available online at 

This SQL statement is adding the new griddisks to the existing diskgroup "DATA" and creating one new failgroup, consisting of all 96 griddisks. The "REBALANCE POWER 512" option tells the system to perform a rebalance operation with a power of 512. It means the system distributes the data evenly across all the disks in the diskgroup using a power of 512.

A. YOU query VSSYSTEM_EVENTS and filter for the event ‘cell physical IO interconnect bytes returned by smart scan’, associated to your table. This does not show how much data was filtered by Smart Scan, but only how much data was returned after Smart Scan12.

C. You query v$SYSTAT and filter for the statistic ‘cell smart table scan’, associated to your table. This does not show how much data was filtered by Smart Scan for a specific table, but only for all tables in a session12.

In the Exadata X9M-2 configuration:

High Capacity (HC) Storage Server: Each HC storage server is equipped with 4 x 6.4 TB NVMe flash cards. These flash cards serve as a cache layer to accelerate I/O performance, especially for read-heavy and mixed workload environments. This configuration combines large storage capacity with NVMe flash for optimal data processing.

Extreme Flash (EF) Storage Server: Each EF storage server contains 8 x 6.4 TB NVMe flash cards, which provides extremely high IOPS and low latency. This configuration is designed for applications demanding high-performance flash storage, making it suitable for intensive OLTP and analytical workloads.

Database Server Flash Storage: The Exadata X9M-2 database servers themselves do not include flash storage as part of their default configuration, which aligns with option D. However, since option E is correct, we do not include D as the other correct answer​​.

Exadata Secure RDMA Fabric isolation is a feature that allows you to use virtualization on the X9M-2 platform while maintaining security and isolation between multiple tenants or VM clusters. Secure Fabric isolation works by creating a dedicated network partition and VLAN ID for each Database VM cluster, which is used for cluster networking between the database servers in the VM Cluster. This ensures that the network traffic of each VM cluster is isolated from the others, and it prevents unauthorized access to the data or resources of other VM clusters. Secure Fabric isolation can also be used for other purposes such as client networking, Data Guard traffic, but it's mainly used to provide security and isolation between multiple tenants or VM clusters.

According to Oracle’s documentation1, Exadata Secure RDMA Fabric Isolation is a feature that enables strict network isolation for Oracle Real Application Clusters (Oracle RAC) clusters on Exadata Database Machine systems that use RDMA over Converged Ethernet (RoCE). Exadata Secure RDMA Fabric Isolation uses RoCE VLANs to ensure that network packets from one VM cluster cannot be seen by another VM cluster. VLAN tag enforcement is done at the KVM host level, which means that security cannot be bypassed by any software exploits or misconfiguration on the database server VMs1.

Therefore, the statement that is true about how Exadata Secure RDMA Fabric isolation is used in X9M-2 with virtualization enabled is:

With Secure Fabric isolation, each Database VM cluster uses a dedicated network partition and VLAN ID for cluster networking between the database servers in the VM Cluster. This provides security and isolation between multiple tenants or VM clusters.

According to Oracle’s documentation1, one of the utilities for diagnostics and repair of Oracle Exadata Storage Server is ExaWatcher, which collects operating system and network metrics on database servers and storage servers. The utility is located in the /opt/oracle.ExaWatcher directory1.

To investigate why an Exadata Database Server stopped communicating on the client network for 10 minutes over the past weekend, you can use the GetExaWatcherResults.sh script to collect and analyze ExaWatcher data for a specified time range1.

Therefore, the command that you should use to investigate this is:

/opt/oracle.ExaWatcher/GetExaWatcherResults.sh —from _17:00:00 —to _23:59:00

In an Exadata environment, the path of communication for SNMP traps involves:

Management Server (MS) Process to EM Agent: Alerts related to the storage server are generated by the MS process, which then forwards SNMP traps directly to the Enterprise Manager agent, allowing centralized monitoring and alert management​.

ILOM to EM Agent: The ILOM on each Exadata storage server can independently send SNMP traps to the EM agent, providing additional hardware-level monitoring and alerting capabilities .

These pathways ensure that alerts from both hardware and software layers reach Enterprise Manager efficiently, supporting proactive management and rapid response to system issues.

According to the Oracle documentation1, two statements that are true about enabling write-back flash cache are:

Write-back flash cache is on by default for High Capacity Storage Servers in High Redundancy configurations (A). This is because write-back flash cache provides better performance and reliability for data file writes than write-through flash cache.

Before write-back flash cache is enabled, you need to drop the Flash Cache first (D). This is because changing the flash cache mode requires recreating the flash cache with a different configuration.

D. ASR can upload configuration metadata to support problem resolution1.

E. ASR Manager opens a service request (SR) automatically after sensors detect hardware faults1

Exadata Database Machine is a pre-configured and pre-tuned hardware and software system designed to run Oracle Database, it can be installed on raised floor environments, but also on concrete or tile floors

Oracle Exadata Database Machine X9M Implementation Essentials states that Exadata racks are designed to be installed on flat surfaces, not raised floor environments. It is not required to install the rack on raised floor environments. Additionally, the other options listed are all requirements for validating, receiving, unpacking, and planning access route and space requirements for Exadata Database Machine. (Source: Oracle Exadata Database Machine X9M Implementation Essentials, page 41)

This command is based on the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and other resources. This command sets the power state of the system to ON and starts the storage server. It is the only command that is able to start the storage server remotely. All the other commands are incorrect or require the user to be physically present in the data center.

Exadata System Software metrics and alerts work as follows:

Persistence of Thresholds: When metric thresholds are configured, they remain active and persist across server reboots. This ensures consistent monitoring behavior even after maintenance or unexpected reboots .

Default Metrics: By default, metrics are collected without predefined thresholds. Administrators must set custom thresholds to enable specific alerting based on their operational requirements​.

Your customer needs to ensure that their data is available on the Exadata machine during updates. The customer wants to be able to update one server at a time but still be protected against single-node server failure. This means that they need a redundancy level that can tolerate at least one disk failure without losing data availability or performance. Therefore, the best option for them is normal redundancy . Normal redundancy provides two-way mirroring by default, which means that each data extent has a primary copy and a mirror copy on different disks in different failure groups1. A failure group is a subset of disks within a disk group that are likely to fail at the same time due to common dependencies2. On Exadata Database Machine , each Storage Server is considered as a failure group by default2. This means that if one Storage Server fails or needs to be updated , the data on its disks can still be accessed from another Storage Server that has the mirror copies of the same data extents2. Therefore, normal redundancy ensures data availability and performance during updates or single-node server failures.

According to Oracle’s documentation12, the components that are monitored directly through the use of Exadata-specific Enterprise Manager Plug-Ins are:

The storage server ILOM2

The Power Distribution Units (PDUs)2

The RDMA over Converged Ethernet (RoCE) switches3

To monitor the effectiveness of Persistent Memory (PMEM) cache usage with RDMA on Exadata, information on RDMA I/O statistics can be found in:

PMEM Cache User Reads section in the AWR Report: This section provides detailed statistics on PMEM read operations, including user reads that leverage RDMA for direct memory access from PMEM. These metrics help gauge the utilization and efficiency of the PMEM cache​.

Exadata Metrics (LIST METRICCURRENT): By using the LIST METRICCURRENT command within the Exadata environment, real-time metrics related to PMEM usage and RDMA I/O statistics can be accessed. This provides an immediate view of the current performance and activity on Exadata’s persistent memory components​.

These tools together offer insights into PMEM cache usage and the effectiveness of RDMA for optimized data access.

B and E are true statements for the Oracle Exadata Configuration Assistant (OECA). OECA facilitates PDU power selection initially and after equipment addition, and it allows for the elastic configuration of the hardware. It does not reconfigure the size of disk groups or recreate grid disks, nor does it allow for a single XT storage server in the configuration. The "Add Equipment" input option does allow for the allocation of RU slots for customer equipment.

References for this information can be found in the Oracle Exadata Database Machine X9M Implementation Essentials Official Text Book and Resources.

Search results: [1] Oracle Exadata Database Machine X8-2 [1][2]: Configuration Assistant Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can … [2] The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can be used to … Add Equipment: This input option allows you to allocate RU slots for … [3] Oracle Exadata Database Machine X7-2 and X7-2L Installation Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can … [4] The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can be used to … Power Selection [1][2]: This input option allows you to select PDU power initially … [5] Oracle Exadata Database Machine X7-2 and X7-2L Installation Guide … The Oracle Exadata Configuration Assistant (OECA) is a web-based tool that can …

A. ZFS Storage Appliance (ZFSSA) can't connect directly to the Exadata 100Gb RoCE network switches. ZFSSA uses Fibre Channel protocol to connect to the Exadata storage cells. C. When backing up multi-rack systems, sharing Exadata X9M switches is not recommended. Each rack should have its own switches to minimize the risk of data loss due to switch failure.

Review the safety guidelines.

Unpack Oracle Exadata Rack.

Let the Exadata acclimatize for 24 hours.

Place Exadata in its allocated space.

Stabilize the Exadata Rack.

Power on Exadata PDU A.

Power on Exadata PDU B.

This order ensures that the necessary safety precautions are taken before installing the Exadata Database Machine, and that the machine is allowed to acclimate to its new environment before being powered on.

Oracle Enterprise Manager (EM) Cloud Control provides comprehensive monitoring and management for Exadata Database Machines, including:

Support for Database Machine Storage Expansion Racks: EM Cloud Control seamlessly integrates with the Storage Expansion Rack, allowing administrators to monitor both primary and expansion storage environments together, which is essential for large-scale deployments​.

Minimal Agent Installation: Cloud Control needs only one Oracle Management Agent on one compute node to monitor the entire Database Machine cluster, covering all compute and storage nodes. This is due to Exadata’s interconnect and resource-sharing capabilities, enabling centralized monitoring with minimal setup requirements​​.

The Oracle Exadata Deployment Assistant Command Line Interface (OEDACU) supports a variety of configuration and lifecycle management tasks for Exadata systems, such as adding or removing nodes, resizing ASM disk groups, and managing Oracle Database home directories. However, it does not support lifecycle management for the Zero Data Loss Recovery Appliance (ZDLRA), as this device requires different management tools specific to its backup and recovery functions .

According to Oracle’s documentation1, to set a threshold for a metric on a database server, you need to use the create threshold command with the appropriate parameters. The set threshold command is used to modify an existing threshold2.

Therefore, the command that you should use to generate alerts for such an event is:

dbmcli -e “create threshold ds_temp comparison=‘>’, critical=30” on each database server1

Oracle Auto Service Request (ASR) on Exadata Database Machines is designed to proactively monitor and detect hardware and software issues. When a problem is detected, ASR Manager automatically opens a service request (SR) with Oracle Support. The primary focus of ASR is on hardware assets, such as storage servers, database servers, and network components, as well as software assets related to Exadata System Software and Oracle Database configurations​​.