1Z0-902 Practice Questions

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.

High Capacity (HC) Storage Server: The Exadata X9M-2 HC storage server is configured with a

combination of hard disks and flash memory, providing a balance of storage capacity and

performance.

It includes 12 x 18 TB hard disk drives, which totals 216 TB of raw disk capacity .

For flash storage, it has 4 x 6.4 TB PCIe flash cards totaling 25.6 TB of flash storage. This configuration

uses NVMe Flash Accelerator F680 cards optimized for database caching  .

The persistent memory in the HC server totals 1.5 TB, enhancing performance for OLTP (Online

Transaction Processing) workloads by providing ultra-fast access speeds compared to traditional flash

storage .

Extreme Flash (EF) Storage Server: The EF storage server in the Exadata X9M-2 model is an all-flash

storage server designed for high IOPS and low latency, making it ideal for performance-intensive

workloads.

This configuration contains 8 x 6.4 TB PCIe flash cards, providing a raw capacity of 51.2 TB of high-

performance flash storage .

In terms of persistent memory, it includes 756 GB of Intel Optane Persistent Memory. This enhances

flash storage performance by offloading data processing directly to persistent memory  .

The Exadata X9M-2 storage configurations—both HC and EF—are optimized for different workload

requirements. The HC configuration caters to larger datasets needing high storage capacity, while the

EF configuration is designed for workloads requiring high throughput and minimal latency.

Oracle ASR covers a range of hardware components on Exadata Database Machines to ensure rapid

response and issue resolution. The covered hardware components include critical parts such as:

Fan Trays: These are essential for cooling Exadata components and are covered by ASR in case of

failures .

System Controller (SC): Integral to the operation of Exadata storage servers, SC failures are reported

by ASR to ensure the overall system’s reliability and availability .

I/O Boards: ASR actively monitors and responds to failures in I/O boards, which are crucial for data

processing and connectivity within Exadata storage servers .

The ASR system is optimized to handle hardware-related issues proactively, ensuring that critical

components are continuously monitored and replaced as necessary.

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  .

Oracle Exadata Deployment Assistant (OEDA) offers multiple benefits for configuring and deploying

Exadata systems:

Configuration Gathering and Rack File Creation: OEDA simplifies the setup of Exadata environments

by collecting system-specific configuration details. It uses this information to generate the Exadata

Rack configuration file, which outlines the optimal setup for the particular environment, streamlining

the deployment process and ensuring compatibility with Oracle best practices .

Lifecycle Management CLI for Exadata Systems: OEDA includes a command-line interface (CLI) that

facilitates various lifecycle management tasks, specifically designed for Exadata systems. This CLI

helps in automating deployment steps, adjusting configurations, and updating system parameters,

tailored specifically for Exadata’s hardware and software environment .

Once the physical disk has been replaced, you will need to create a new celldisk and griddisks on the

replaced physical disk. After the griddisks have been dropped from the associated ASM diskgroups,

you can then add the griddisks back into the ASM diskgroup they used to be a member of and

rebalance the data on the effected griddisks. Finally, you should verify that the griddisks located on

the physical disk have been successfully dropped from the associated ASM diskgroups.

To enable the write-back flash cache on an Exadata X9M-8 storage cell, the existing flash cache must

be removed before transitioning to a new mode. This is because the flash cache configuration—

whether set to write-through or write-back—requires a re-initialization of the flash storage to apply

the new caching behavior. The steps are as follows:

Drop the Existing Flash Cache: Before altering the cache mode, any existing flash cache on the cell

must be dropped. This clears the existing configuration and allows the system to reallocate flash

resources under the new mode. The command for this is:

# cellcli -e "drop flashcache"

Create a New Flash Cache in Write-Back Mode: After dropping the existing flash cache, you can

create a new flash cache with write-back mode enabled. This step ensures that the flash cache is

configured correctly to handle write operations before they reach disk, thus accelerating write-heavy

workloads. The relevant command to set write-back mode is:

# cellcli -e "create flashcache all"

This process will reset the flash cache with the write-back mode enabled, thereby caching both read

and write operations effectively  .

The given command uses a for loop with ipmitool to issue ping commands sequentially to a range of

IP addresses in the management network:

for j in {01..23}; do ipmitool sunoem cli "set /SP/network/test ping=192.168.1.1$j"; done

This script verifies the connectivity of the ILOM management network before the Exadata

installation. Each server’s Service Processor (SP) is tested for reachability, confirming that the

management network setup is operational across the full rack .

Statement B is true as the vm_maker —start-domain command can be used to start a virtual

machine manually, as stated in the Oracle Exadata Database Machine X9M Implementation

Essentials Official Text Book (page 65).

Statement E is also true as the vm_maker —auto-start command can be used to configure a virtual

machine to start automatically when the KVM host is started [1][2], as stated in the Oracle Exadata

Database Machine X9M Implementation Essentials Official Text Book (page 66).

According to the Oracle Auto Service Request (ASR) documentation1, ASR raises service requests for qualified Oracle products that are detected with specific faults. The qualified Exadata products include2: Database servers Storage servers InfiniBand switches Cisco switches (X8M and later systems) Power distribution units (PDUs)