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

According to the web search results123, the storage servers in an Exadata Database Machine are mainly used for processing data at the storage level and offloading some SQL operations from the database servers. Therefore, the two activities that are supported on the storage servers are:

• A. changing the root password
• E. configuring secure shell user equivalency for the cellmonitor user

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmso/exadata-introduction.html

The statements that are true about the CellCLI command are:

• It has command-line history . According to 1, you can use the up and down arrow keys to scroll through previous commands that you entered in CellCLI . You can also use Ctrl+R to search for a previous command by entering part of it .
• It can be executed on storage servers . According to 1, you can invoke CellCLI by logging in to the Exadata cell as cellmonitor , celladmin , or root user and typing “cellcli” . Within CellCLI , you can perform various management and monitoring tasks for the cell134.
• It can be executed using the DCLI utility . According to 5, DCLI (distributed CLI) is another utility that can be used to execute scripts and commands across multiple storagecells from a single interface. You can use DCLI to run CellCLI commands on multiple cells at once54.

• It collects configuration information automatically (B). OCM gathers detailed configuration information about a variety of designated Oracle products and components across an enterprise on a regular basis2.
• It collects configuration information on demand ©. OCM can also collect configuration information manually when requested by the user or by Oracle Support2.
• Collected configuration information can be uploaded automatically to Oracle (E). OCM can upload the collected configuration information to My Oracle Support automatically for analysis and support purposes3.

According to Oracle’s documentation1, the client network on Exadata X9M-2 Database Server is used for client access to the database servers using Single Client Access Name (SCAN) and Oracle RAC Virtual IP (VIP) addresses. To verify that the client network is available via both client switches, you can use the command:

• cat /proc/net/bonding/bondeth0

This command displays information about the bondeth0 interface, which is used for the client network on Exadata X9M-2 Database Server2. You can check if both interfaces (eth0 and eth1) are active and connected to different switches3.

In order to monitor all components of this multirack configuration, Enterprise Manager agents must be deployed on at least two storage servers in both racks and all database servers in both racks. This is according to the Oracle Exadata Database Machine X9M Implementation Essentials official text book [1], in which it states "To monitor all components of the multirack configuration, you must deploy agents on all database servers and at least two storage servers in each rack" (page 6-15).

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.

https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-administering-asm.html

• Option C shows the number of read hits from PMEM cache on storage servers which indicates how much data was served from PMEM instead of flash or disk1.
• Option E shows detailed information about PMEM cache such as size, utilization, hit ratio, read latency and write latency2.

The two valid reasons are:

• corruption in the / (root) filesystem . According to 1, this is one of the scenarios that requires a storage server rescue procedure , because it prevents the storage server from booting up normally . The rescue procedure will re-image the root filesystem with a fresh copy of the operating system and restore the configuration files from a backup1.
• the failure of both physical M.2 disks . According to 2, each Exadata Storage Server X9M-2 has two physical M.2 disks that store the operating system and configuration files for the storage server . If both M.2 disks fail , then the storage server cannot boot up or function properly . The rescue procedure will replace the failed M.2 disks with new ones and re-image them with the operating system and configuration files2.

The correct sequence is:

• uk.co.certification.simulator.questionpool.PList@ddad710

• uk.co.certification.simulator.questionpool.PList@ddad780

• uk.co.certification.simulator.questionpool.PList@ddad880

• uk.co.certification.simulator.questionpool.PList@ddad910

• uk.co.certification.simulator.questionpool.PList@ddad980