Oracle Exadata X5 Administration Free Sample Questions

C

A, C -- Explanation:
A: Oracle recommends that you install Oracle ASR Manager on an external, standalone server.
C: Oracle ASR is designed to generate Oracle service requests automatically when certain types of faults are detected on Oracle products that are qualified for Oracle ASR.
Oracle ASR works only for specific component faults. Most of the common components, such as disks, fans, and power supplies, are covered. However, some components are not covered. For example, Oracle ASR does not cover InfiniBand events; there are specific images and specific InfiniBand switch firmware that you must use. You cannot upgrade these components independently.
Incorrect answers:
D: Oracle recommends that you install Oracle ASR Manager on an external, standalone server. -- References: http://docs.oracle.eom/cd/E80920 01/ASXQI/toc.htm#GUID-490B2837-C608-4626-B4FF-59F679C36302

D, E -- Explanation:
D: In-Memory Columnar Caching on cells is enabled by default when the INMEMORYJSIZE is configured. You do not need to do anything to get this enhancement.
E: Columnar Flash Caching implements a dual format architecture in Exadata flash by automatically transforming frequently scanned Hybrid Columnar Compressed data into a pure columnar format as it is loaded into the flash cache.
Incorrect answers:
F: Columnar Flash Caching accelerates reporting and analytic queries while maintaining excellent performance for OLTP style single row lookups. -- References:
http://docs.oracle.eom/cd/E80920 01/SAGUG/exadata-storage-server-monitoring.htm#SAGUG20883 http://www.oracle.com/technetwork/database/exadata/exadata-x5-8-ds-2745934.pdf

B, C --

C, E, F -- Explanation:
C: The decompression process typically takes place on the Oracle Exadata Storage Server in order to maximize performance and offload processing from the database server.
E: A logical construct called the compression unit is used to store a set of hybrid columnar compressed rows. When data is loaded, column values for a set of rows are grouped together and compressed. After the column data for a set of rows has been compressed, it is stored in a compression unit.
F: What happens when I update a row on compressed tables? What about locks? • BASIC and OLTP: the updated row stays in the compressed block ‘usual’ Oracle’s row-level locks . Hybrid columnar: Updated row is moved, as in a delete + insertHow to see that? With dbms_rowid packageNew row is OLTP compressed if possibleLock affects the entire CU that contains the row
Note: Oracle’s Hybrid Columnar Compression technology is a new method for organizing data within a database block. As the name implies, this technology utilizes a combination of both row and columnar methods for storing data. This hybrid approach achieves the compression benefits of columnar storage, while avoiding the performance shortfalls of a pure columnar format.
Incorrect answers:
B: Data remains compressed not only on disk, but also remains compressed in the Exadata Smart Flash Cache, on Infiniband, in the database server buffer cache, as well as when doing back-ups or log shipping to Data Guard. -- References: http://www.oracle.com/technetwork/database/exadata/ehcc-twp-131254.pdf

C, D, E, F -- Explanation:
CD: That data remains compressed not only on disk, but also remains compressed in the Exadata Smart Flash Cache, on Infiniband, in the database server buffer cache, as well as when doing back-ups or log shipping to Data Guard.
E (not B): Use the Write-Back Flash Cache feature to leverage the Exadata Flash hardware and make Exadata Database Machine a faster system for Oracle Database Deployments. Write-through cache mode is slower than write-back cache mode. However, write-back cache mode has a risk of data loss if the Exadata Storage Server loses power or fails.
F: Storage indexes are not stored on disk; they are resident in the memory of the storage cell servers.
Incorrect answers:
A: Storage indexes are not stored on disk; they are resident in the memory of the storage cell servers. They are created automatically after the storage cells receive repeated queries—with predicates—for columns. No user intervention is needed to create or maintain storage indexes. And because they are memory-resident structures, they disappear when the storage cells are rebooted. -- References: http://www.oracle.com/technetwork/testcontent/o31exadata-354069.html