Evaluate the following statements:
CREATE TABLE purchase_orders
(pojd NUMBER(4),
po_date TIMESTAMP,
supplie_id NUMBER(6),
po_total NUMBER(8,2),
CONSTRAINT order_pk PRIMARY KEY(po_id))
PARTITION BY RANGE(po_date)
(PARTITION Q1 VALUES LESS THAN (TO_DATE(?1-apr-2007?d-mon-yyyy?),
PARTITION Q2 VALUES LESS THAN (TO_DATE(?1-jul-2007?d-mon-yyyy?),
PARTITION Q3 VALUES LESS THAN (TO_DATE(?1-oct-2007?d-mon-yyyy?),
PARTITION Q4 VALUES LESS THAN (TO_DATE(?1-jan-2008?d-mon-yyyy?));
CREATE TABLE purchase_order_items
(po_id NUMBER(4) NOT NULL, product_id NUMBER(6) NOT NULL,
unit_price NUMBER(8,2),
quantity NUMBER(8),
CONSTRAINT po_items_fk
FOREIGN KEY (po_id) REFERENCES purchase_orders(po_id))
PARTITION BY REFERENCE(po_items_fk);
What are the two consequences of the above statements? (Choose two.)

• A. Partition maintenance operations performed on the PURCHASEJDRDERJTEMS table are automatically reflected in the PURCHASEjDRDERS table.
• B. Partitions of PURCHASE_ORDER_ITEMS have system-generated names.
• C. The PURCHASEJDRDERJTEMS table inherits the partitioning key from the parent table by automatically duplicating the key columns.
• D. Partitions of the PURCHASEJDRDERJTEMS table exist in the same tablespaces as the partitions of the PURCHASEJDRDERS table.
• E. Both PURCHASEjDRDERS and PURCHASEJDRDERJTEMS tables are created with four partitions each.

You executed the following PL/SQL block successfully:
VARIABLE tname VARCHAR2(20)
BEGIN
dbms_addm.insert_finding_directive (NULL, DIR_NAME=>'Detail CPU Usage1,
FINDING_NAME=>'CPU Usage1,
MIN_ACTIVE_SESSIONS=>0,MIN_PERC_IMPACT=>90);
:tname := 'database ADDM task4';
dbms_addm.analyze_db(:tname, 150,162);
END;
/
Then you executed the following command:
SQL> SELECT dbms_addm.get_report(:tname) FROM DUAL;
The above command produces Automatic Database Diagnostic Monitor (ADDM)
analysis____.

• A. with the CPU Usage finding for snapshots not between 150 and 162
• B. with the CPU Usage finding if it is less than 90
• C. without the CPU Usage finding if it is less than 90
• D. with the CPU Usage finding for snapshots below 90

You are managing an Oracle Database 11 g instance with ASM storage. You lost an ASM disk group DATA. You have RMAN backup of data as well as ASM metadata backup.
You want to re-create the missing disk group by using the ASMCMD md_restore command. Which of these methods would you use to achieve this? (Choose all that apply.)

• A. Restore the disk group with changed disk group specification, failure group specification,
  disk group name, and
  other disk attributes.
• B. Restore the disk group with the exact configuration as the backed-up disk group, using
  the same disk group
  name, same set of disks, and failure group configurations.
• C. Restore the disk group with the exact configuration as the backed-up disk group, using
  the same disk group name, same set of disks, failure group configurations, and data on the
  disk group.
• D. Restore metadata in an existing disk group by passing the existing disk group name as
  an input parameter.

You need to create a partitioned table to store historical data and you Issued the following command:
CREATE TABLE purchas_interval
PARTITION BY RANGE (time_id)
INTERVAL (NUMTOYMINTERVAL(1 ,'month1)) STORE IN (tbs1 ,tbs2,tbs3)
PARTITION p1 VALUES LESS THAN(TO_DATE('1-1-2005I, 'dd-mm-yyyy')),
PARTITION p2 VALUES LESS THAN(TO_DATE('1-1-2007', 'dd-mm-yyyy')))
AS
SELECT *
FROM purchases
WHERE time_id < TO_DATE('1-1-2007'l'dd-mm-yyyy');
What is the outcome of the above command?

• A. It creates two range partitions of varying range. For data beyond '1-1-2007,' it creates partitions with a width of |_| one month each
• B. It creates two range partitions (P1, P2). Within each range partition, it creates monthwise subpartitions.
• C. It returns an error because the number of tablespaces (TBS1 ,TBS2,TBS3)specified does not match the number of range partitions (P1 ,P2) specified.
• D. It returns an error because the range partitions P1 and P2 should be of the same range.