Difficulty: Easy
Correct Answer: Incorrect
Explanation:
Introduction / Context:
Triggers are server-side routines that fire in response to data changes. Understanding their types and timing is essential for data integrity, auditing, and automation. The prompt suggests that the three types are BEFORE, AFTER, and EXCEPTION. This question checks whether that classification aligns with standard and widely used vendor terminology.
Given Data / Assumptions:
Concept / Approach:
Standard terminology distinguishes triggers by timing relative to the triggering DML event: BEFORE and AFTER. Many vendors additionally support INSTEAD OF triggers (especially for updatable views), which replace the action rather than firing before or after it. “EXCEPTION” is not a standard timing type for triggers; exception handling is usually done within procedural code blocks, not as a trigger category. Thus the proposed trio is inaccurate.
Step-by-Step Solution:
Verification / Alternative check:
Review vendor docs: you find BEFORE/AFTER universally; EXCEPTION does not appear as a trigger kind. Some RDBMS provide statement-level versus row-level options, but those are orthogonal to timing types.
Why Other Options Are Wrong:
Common Pitfalls:
Mixing exception blocks with trigger timing; forgetting INSTEAD OF triggers for view updates; assuming vendor-specific features are universal.
Final Answer:
Incorrect
Discussion & Comments