1z1-902 無料問題集「Oracle Exadata Database Machine X8M Implementation Essentials」

（A）# /opt/oracle.SupportTools/exachk/exachk -from <Fridays_Date>_17:00:00 -to <Sundays_Date>_23:59:00

（B）# /opt/oracle.ExaWatcher/GetExaWatcherResults.sh -from <Fridays_Date>_17:00:00 -to <Sundays_Date>_23:59:00

（C）# /opt/oracle.SupportTools/ibdiagtools/netcheck/runDiagnostics.pm -from <Fridays_Date>_17:00:00 -to <Sundays_Date>_23:59:00

（D）$ ${ORACLE_HOME}/suptools/tfa/release/tfa_home/bin/tfact1 -from <Fridays_Date>_17:00:00 -to <Sundays_Date>_23:59:00

（A）If High redundancy is selected, grid disks from the primary and secondary Exadata Database Machine must be specified.

（B）Sparse diskgroups are virtual objects allocated from the DATA diskgroup.

（C）In an Exadata storage server, each disk is placed into a separate failure group.

（D）The grid disks in ASM diskgroups must have similar performance characteristics in addition lo having the same size.

（E）Extreme Flash (EF) and High Capacity (HC) disks can be mixed to any capacity within the same diskgroup.

（A）No thresholds need to be set because they are preset in the ILOM and these are sufficient for monitoring.

（B）Set thresholds in ILOM and in Enterprise Manager because they are not preset anywhere and must be set in both places.

（C）No thresholds need to be set because they are preset in the ILOM and in Enterprise Manager

（D）Set thresholds only in ILOM because they are not preset anywhere but need to be set only in ILOM.

（A）OEDA facilitates abstracting hardware.

（B）OEDA provides a CL1 which supports life cycle management tasks for Exadata systems only.

（C）OEDA gathers configuration details and creates the Oracle Exadata Rack configuration file.

（D）OEDA is used for Oracle Exadata Database Machine, Zero Data Loss Recovery Appliance, Private Cloud Appliance, and SuperCluster.

（E）OEDA Web-based user interface cannot import OEDA XML configuration files created with the Java-based version of OEDA without conversion

（A）2,3,4,6,1,7,5

（B）3,2,6,1,4,7,5

（C）4,3,2,6,1,7,5

（D）3,2,6,4,1,7,5

（E）2,6,1,4,3,7,5

（A）Identify the griddisks located on the failed physical disk and drop them from the associated ASM diskgroups.

（B）Rebalance the data on the effected griddisks before performing a manual drop command.

（C）Replace the failed physical disk.

（D）Create a new celldisk and new griddisks on the replaced physical disk.

（E）Add the griddisks back into the ASM diskgroup they used to be a member of.

（F）Verify that the griddisks located on the physical disk have been successfully dropped from the associated ASM diskgroups.

（A）ifconfig -a legrep "re0| re1"

（B）/opt/oracle.SupportTools/ibdiagtools/checkbadlinks.p1 -all

（C）cat /proc/net/bonding/bondeth0

（D）netstat -rn

（A）the storage server ILOM

（B）the RDMA over Converged Ethernet (RoCE) switches

（C）Hybrid Columnar Compression (HCC) ratios on Extended (XT) storage servers

（D）Oracle clusterware on the database server

（E）the Power Distribution Units (PDUs)

（F）ASM instances

（A）on all database servers in the second rack

（B）on all database servers in the first rack

（C）on all storage servers in both racks

（D）on all database servers and at least two storage servers in both racks

（E）on all database servers in both racks and one storage server in each rack

（F）on only one database server in both racks

（G）on at least two storage servers in both racks