1z0-070 Sample Questions & Answers

B, C --

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, 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, 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

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

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

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

A, C, E -- Explanation:
The default schedule of scrubbing is every two weeks. -- References: docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm">http://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm

A, C, E -- Explanation:
The default schedule of scrubbing is every two weeks. -- References: docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm">http://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm

A, C, E -- Explanation:
The default schedule of scrubbing is every two weeks. -- References: docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm">http://docs.oracle.com/cd/E80920_01/DBMMN/maintaining-exadata-storage-servers.htm

C, E -- Explanation:
C: ILOM supports the Intelligent Platform Management Interface (IPMI), which enables you to monitor and control your server platform, as well as to retrieve information about your server platform.
ILOM supports alerts in the form of IPMI Platform Event Trap (PET) alerts. Alerts provide advance warning of possible system failures.
E: Oracle ILOM supports the Simple Network Management Protocol (SNMP), which is used to exchange data about network activity.
SNMP functionality requires the following two components: . Network management station - A network management station hosts management applications, which monitor and control managed nodes. . Managed node - A managed node is a device such as a server, router, or hub that hosts SNMP management agents that are responsible for carrying out requests from management stations, such as a service processor (SP) running Oracle ILOM. Managed nodes can also provide unsolicited status information to a management station in the form of a trap. -- References: docs.oracle.com/cd/E19860-01/E21452/E21452.pdf">https://docs.oracle.com/cd/E19860-01/E21452/E21452.pdf

C, E -- Explanation:
C: ILOM supports the Intelligent Platform Management Interface (IPMI), which enables you to monitor and control your server platform, as well as to retrieve information about your server platform.
ILOM supports alerts in the form of IPMI Platform Event Trap (PET) alerts. Alerts provide advance warning of possible system failures.
E: Oracle ILOM supports the Simple Network Management Protocol (SNMP), which is used to exchange data about network activity.
SNMP functionality requires the following two components: . Network management station - A network management station hosts management applications, which monitor and control managed nodes. . Managed node - A managed node is a device such as a server, router, or hub that hosts SNMP management agents that are responsible for carrying out requests from management stations, such as a service processor (SP) running Oracle ILOM. Managed nodes can also provide unsolicited status information to a management station in the form of a trap. -- References: docs.oracle.com/cd/E19860-01/E21452/E21452.pdf">https://docs.oracle.com/cd/E19860-01/E21452/E21452.pdf

B, D -- Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1; Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1;Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100*free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1; The example above shows that the DATAC1 disk group has only about 15% of free space available while the RECOC1 disk group has about 87% free disk space. The PCT_FREE displayed here is raw free space, not usable free space. Additional space is needed for rebalancing operations. -- References: docs.oracle.com/cd/E80920_01/SAGUG/exadata-administering-asm.htm#SAGUG20526">http://docs.oracle.com/cd/E80920_01/SAGUG/exadata-administering-asm.htm#SAGUG20526

B, D -- Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1; Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1;Explanation:
Determine the Amount of Available Space To increase the size of the disks in a disk group you must either have unallocated disk space available, or you have to reallocate space currently used by a different disk group.
Example: View the space currently used by the disk groups.
SELECT name, totaljTib, free_mb, total_mb - free_mb used_mb, round(100*free_mb/total_mb,2) pct_free FROM v$asm_diskgroup ORDER BY 1; The example above shows that the DATAC1 disk group has only about 15% of free space available while the RECOC1 disk group has about 87% free disk space. The PCT_FREE displayed here is raw free space, not usable free space. Additional space is needed for rebalancing operations. -- References: docs.oracle.com/cd/E80920_01/SAGUG/exadata-administering-asm.htm#SAGUG20526">http://docs.oracle.com/cd/E80920_01/SAGUG/exadata-administering-asm.htm#SAGUG20526