Oracle Database and PL/SQL Concepts

Database procedures are stored in compiled form within the database. This compilation happens when the procedure is created, improving execution performance compared to interpreting source code each time. The database engine stores the compiled execution plan, not the original source.

A UNIQUE constraint prevents duplicate values in the column. If multiple rows are inserted with SYSDATE, they will have identical date-time values (down to the second) when inserted in rapid succession, causing constraint violations. Even if inserted at different times, the constraint will reject any duplicates, so it won't reliably accept all SYSDATE inserts.

In Oracle SQL, the concatenation operator (||) treats NULL as an empty string, not as a NULL value that propagates. Therefore 'AXA'||NULL becomes 'AXA', and then ||'US' produces 'AXAUS'. This is different from arithmetic operations where NULL + anything = NULL.

This is a correlated subquery finding salaries where fewer than 3 other employees have lower salaries. Count employees with salary less than each E1.SAL: for 5750, count=4 (all others lower); for 5000, count=2; for 3500, count=1; for 2850, count=0. Condition 3 > count is true for salaries 5000, 3500, 2850 where count is 2, 1, 0 respectively.

A database trigger is a procedural block of logic written in PL/SQL (or another procedural language) that is automatically executed or fired by the database engine in response to a specified SQL event, such as an INSERT, UPDATE, or DELETE statement.

A transaction in a database management system terminates either when it is explicitly committed (making changes permanent) or when it is rolled back (undoing all changes). These are the two standard ways to end a transaction. Simply executing DML statements doesn't end a transaction - the database waits for an explicit COMMIT or ROLLBACK command.

Triggers are database objects that automatically execute in response to specific data manipulation events. The three primary DML events that can fire triggers are INSERT (when new rows are added), UPDATE (when existing rows are modified), and DELETE (when rows are removed). Options like Define, Create, Drop, and Comment are DDL operations, not trigger events.

COUNT(SAL) counts the number of non-NULL values in the SAL column. Looking at the data: John has 3250, Praveen has 2000, Prasanth has 5500, Vikram has 6650, but Mahesh (E300) has no salary listed (NULL). Therefore there are 4 non-NULL salary values, so COUNT(SAL) returns 4.

DML (Data Manipulation Language) encompasses all SQL statements that manipulate data stored in database objects. The primary DML operations are INSERT (add new data), UPDATE (modify existing data), DELETE (remove data), and SELECT (retrieve/query data). All four options represent valid DML statements.

The condition a > b (5 > NULL) evaluates to NULL/UNKNOWN because any comparison with NULL returns NULL. In SQL/PLSQL, NULL AND FALSE/TRUE = NULL (falsy). Since the AND condition short-circuits on the NULL result from a > b, the entire condition is false, the IF block doesn't execute, and 'a' remains unchanged at 5.

RECORD is the odd one out because it's a composite/structured data type that can hold multiple fields of different types (like a struct), while VARCHAR2, BOOLEAN, and RAW are all scalar/primitive data types that hold single values. RECORD is used in PL/SQL for defining complex data structures, not for storing individual values in columns.

Database procedures are stored in compiled form within the database. This compilation happens when the procedure is created, improving execution performance compared to interpreting source code each time. The database engine stores the compiled execution plan, not the original source.

A UNIQUE constraint prevents duplicate values in the column. If multiple rows are inserted with SYSDATE, they will have identical date-time values (down to the second) when inserted in rapid succession, causing constraint violations. Even if inserted at different times, the constraint will reject any duplicates, so it won't reliably accept all SYSDATE inserts.

In SQL string concatenation using the || operator, NULL is treated as an empty string, not as a null terminator. Therefore 'AXA' + empty string + 'US' = 'AXAUS'. This is standard SQL behavior where NULL in string concatenation acts like ''.

The nested query counts how many employees have salary LESS than the current employee (E1.SAL > E2.SAL). The condition 3 > count(*) means we want salaries where at most 2 other salaries are lower. For 3500: only 2850 is lower (count=1). For 5000: 3500 and 2850 are lower (count=2). For 2850: none are lower (count=0). For 5750: three are lower (count=3, fails condition).

A trigger is indeed a piece of logic (typically written in PL/SQL in Oracle databases) that automatically executes in response to specific SQL events like INSERT, UPDATE, or DELETE operations on a table. Therefore both A and B are correct.

A transaction in a database is a logical unit of work that must either complete entirely (COMMIT) or be completely undone (ROLLBACK). These are the only two ways a transaction can terminate - partial completion is not allowed in ACID-compliant databases.

To solve this question, the user needs to know about the DUAL table in Oracle databases.

The DUAL table is a one-row, one-column table that is automatically created by Oracle. It is owned by the SYS user and is accessible to all users.

Therefore, the correct answer is:

The Answer is: C. sys

When you drop a table in a database, the synonym remains as a separate database object but becomes invalid or broken. The synonym is not automatically dropped along with the table - it continues to exist but points to a non-existent object. This is why False is the correct answer.