Question 18

Explanation

Correct options:

1. Query any table in a database – Requires system privilege
   Accessing tables outside your schema generally requires the SELECT ANY TABLE system privilege.

2. Log into a database – Does not require system privilege
   Logging into a database simply requires a valid user account with authentication privileges.

Incorrect options

• Access flat files via a database, which are stored in an operating system directory – Requires system privilege
  Accessing external files typically requires the READ ANY FILE or ADMINISTER DATABASE TRIGGER system privilege.

• Execute a procedure in another schema – Requires system privilege
  Since you lack EXECUTE ANY PROCEDURE, executing another schema’s procedure would require explicit privileges or system-level access.

• Use the WITH GRANT OPTION clause – Does not require system privilege
  The WITH GRANT OPTION can be used if you already have privileges granted to you with that option.

• Truncate a table in another schema – Requires system privilege
  Truncating a table outside your schema would typically require the ALTER ANY TABLE or DROP ANY TABLE system privileges.

When multiple users can access database objects, authorization can be controlled to these objects with privileges. Every object has an owner. Privileges control if a user can modify an object owned by another user. Privileges are granted or revoked either by the instance administrator, a user with the ADMIN privilege or, for privileges to a certain object, by the owner of the object.

A System Privilege is the right to perform a particular action or to perform an action on any object of a particular type. Objects include tables, views, materialized views, synonyms, indexes, sequences, cache groups, replication schemes and PL/SQL functions, procedures and packages. Only the instance administrator or a user with ADMIN privilege can grant or revoke system privileges.

The system privileges can be passed WITH ADMIN OPTION.

An Object Privilege is the right to perform a particular action on an object or to access another user's object. Objects include tables, views, materialized views, indexes, synonyms, sequences, cache groups, replication schemes and PL/SQL functions, procedures and packages.

An object's owner has all Object Privileges for that object, and those privileges cannot be revoked. The object's owner can grant object privileges for that object to other database users. A user with ADMIN privilege can grant and revoke object privileges from users who do not own the objects on which the privileges are granted.

Some privileges confer other privileges. For example, ADMIN privilege confers all other privileges.

All users of the database have the PUBLIC role. In a newly created TimesTen database, by default PUBLIC has SELECT and EXECUTE privileges on various system tables and views and PL/SQL functions, procedures and packages. Privileges that are granted to PUBLIC as part of database creation cannot be revoked.

The object privileges can be passed WITH GRANT OPTION.

TRUNCATE TABLE

TRUNCATE TABLE command requires user to have "drop any table" permission.

TRUNCATE ANY TABLE is a system privilege.