BOOK_SEQ is an existing sequence in your schema.
Which two CREATE TABLE commands are valid?

• A.CREATE TABLE bookings (
  bk_id NUMBER(4) DEFAULT book_seq.NEXTVAL PRIMARY KEY,
  start_date DATE DEFAULT SYSDATE,
  end_date DATE DEFAULT SYSDATE NOT NULL);
• B.CREATE TABLE bookings (
  bk_id NUMBER(4) NOT NULL DEFAULT book_seq.CURRVAL,
  start_date DATE NOT NULL,
  end_date DATE DEFAULT SYSDATE);
• C.CREATE TABLE bookings (
  bk_id NUMBER(4) NOT NULL PRIMARY KEY,
  start_date DATE NOT NULL,
  end_date DATE DEFAULT SYSDATE);
• D.CREATE TABLE bookings (
  bk_id NUMBER(4) DEFAULT book_seq.CURRVAL,
  start_date DATE DEFAULT SYSDATE,
  end_date DATE DEFAULT start date);
• E.CREATE TABLE bookings ( bk_id NUMBER(4),
  start_date DATE DEFAULT SYSDATE,
  end_date DATE DEFAULT (end_date >= start_date));

Comment: *

Name: *

Email: *

Verification: *

Which three statements are true regarding the SQL WHERE and HAVING clauses? (Choose three.)

• A.The HAVING clause conditions can use aliases for the columns.
• B.The WHERE and HAVING clauses cannot be used together in a SQL statement.
• C.The HAVING clause conditions can have aggregating functions.
• D.The WHERE clause is used to exclude rows before grouping data.
• E.The HAVING clause is used to exclude one or more aggregated results after grouping data.

Comment: *

Name: *

Email: *

Verification: *

View the Exhibit and examine PRODUCTS and ORDER_ITEMS tables.

You executed the following query to display PRODUCT_NAME and the number of times the product has been ordered:
SELECT p.product_name, i.item_cnt
FROM (SELECT product_id, COUNT (*) item_cnt
FROM order_items
GROUP BY product_id) i RIGHT OUTER JOIN products p
ON i.product_id = p.product_id;
What would happen when the above statement is executed?

• A.The statement would not execute because the ITEM_CNT alias cannot be displayed in the outer query.
• B.The statement would not execute because the GROUP BY clause cannot be used in the inline view.
• C.The statement would execute successfully to produce the required output.
• D.The statement would not execute because inline views and outer joins cannot be used together.

Comment: *

Name: *

Email: *

Verification: *

Examine the structure of the EMPLOYEEStable:

There is a parent/child relationship between EMPLOYEE_IDand MANAGER_ID.
You want to display the name, joining date, and manager for all employees. Newly hired employees are yet to be assigned a department or a manager. For them, 'No Manager' should be displayed in the MANAGERcolumn.
Which SQL query gets the required output?
SELECT e.last_name, e.hire_date, NVL(m.last_name, 'No Manager') Manager

• A.FROM employees e LEFT OUTER JOIN employees m
  ON (e.manager_id = m.employee_id);
  SELECT e.last_name, e.hire_date, NVL(m.last_name, 'No Manager') Manager
• B.FROM employees e RIGHT OUTER JOIN employees m
  ON (e.manager_id = m.employee_id);
  SELECT e.last_name, e.hire_date, NVL(m.last_name, 'No Manager') Manager
• C.FROM employees e NATURAL JOIN employees m
  ON (e.manager_id = m.employee_id).
• D.FROM employees e JOIN employees m
  ON (e.manager_id = m.employee_id);
  SELECT e.last_name, e.hire_date, NVL(m.last_name, 'No Manager') Manager

Comment: *

Name: *

Email: *

Verification: *

Which three statements are true about Data Manipulation Language (DML)? (Choose three.)

• A.INSERTstatements can insert NULLS explicitly into a column.
• B.DML statements require a primary key be defined on a table.
• C.INSERT INTO...SELECT...FROMstatements automatically commit.
• D.UPDATE statements can have different subqueries to specify the values for each updated column.
• E.DELETEstatements can remove multiple rows based on multiple conditions.

Comment: *

Name: *

Email: *

Verification: *