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

（A）Cell Offload Quarantine

（B）Database Quarantine

（C）Disk Region Quarantine

（D）SQL Plan Quarantine

（E）Manually created Quarantine

（A）When enabling write-back flash cache in a non-rolling manner, you need to drop the Persistent Memory Commit Accelerator (PMEMLog) first.

（B）When enabling write-back flash cache in a rolling manner, DBCLI should be used to inactivate the grid disks on all cells first.

（C）Write-back Flash Cache cannot be used on Extreme Flash Storage Servers.

（D）Write-back flash cache is on by default for High Capacity Storage Servers in High Redundancy configurations.

（E）Before write-back flash cache is enabled, you need to drop the Flash Cache first.

（A）4 x 6.4 TB NVMe flash cards on the database server

（B）4 x 6.4 TB NVMe flash cards on the High Capacity (HC) storage server

（C）8 x 6.4 TB NVMe flash cards on the Extreme Flash (EF) storage server

（D）No flash storage on the database server

（E）8x 6.4 TB NVMe flash cards on the Extended (XT) storage server

（A）Purchase the recommended x86 64-Bit gateway hardware from Oracle.

（B）Install on Oracle Database Appliance.

（C）Install in Oracle Virtual Machine with required hardware.

（D）Provide individual x86 64-Bit gateway hardware.

（E）Install on Exadata Engineered System.

（A）Install Oracle Rest Data Services on each Database server and install the MS APEX application.

（B）The MS Process on the storage servers is natively endowed with REST services and are enabled by default, however, appropriate roles and users should be created to ensure security.

（C）The MS Process on the storage servers is natively endowed with REST services, but are not enabled by default.

（D）Install Oracle Rest Data Services on each Storage server and install the MS APEX application.

（A）2048GB

（B）1024GB

（C）1536GB

（D）512GB

（E）768GB

（F）384GB

（A）Persistent Memory Commit Accelerator helps to further reduce redo log write latency by using Persistent Memory and Remote Direct Memory Access (RDMA).

（B）Persistent Memory Commit Accelerator tracks changes to Persistent Memory Data Accelerator to ensure duplicate blocks are not written to Flash.

（C）Persistent Memory Commit Accelerator reduces redo log write latency by using Persistent Memory and RDMA before flushing to Flash then disk.

（D）Persistent Memory Commit Accelerator copies redo log data from disk for faster redo apply on Data Guard Standby Databases.

（E）Persistent Memory Commit Accelerator contains logging information from all tiers of the software stack for rapid triage and diagnostics.

（A）alert logs for the prod database instances

（B）alert logs for the ASM instances

（C）alert logs for Enterprise Manager

（D）Enterprise Manager Alerts on the Exadata Storage Server Grid home page

（E）Enterprise Manager Alerts on the ILOM home page for cell connectivity problems for the prod database instances

（A）There is free space available on flashdisks inside the Exadata storage servers for possible use for storage indexes.

（B）The DATA_<DBM_Name> and RECO_<DBM_NAME> ASM diskgroups are built on with DATA on the outer-most tracks and RECO on the inner-most tracks of the physical disk.

（C）There is free space available on the hard disks inside the database servers for possible extension of the /uoi file system.

（D）The sparse_<DBM_NAME> diskgroup is created automatically.

（E）There is free space available on flashdisks inside the Exadata storage servers to configure Exadata Smart Flash Logs.