987. Audit customer email — trigger case 3

DBMS Published 30 Sept 2026 Updated 30 Sept 2026 0 Views Verified

Implement the database trigger for this integrity/audit requirement. Consider NULL-safe comparisons and transaction behavior.

Looking for the latest Sarkari Result 2026 updates? Check the latest government exam results, merit lists and result updates on Sarkari Resultess.

Answer & Explanation

4 Answers

Verified

Option A

Use a SELECT-only query and do not enforce the rule.

Additional Explanation

This option is incorrect for the stated requirement.

Verified

Option B

Use a trigger that recursively updates the same table without safeguards.

Additional Explanation

This option is incorrect for the stated requirement.

Verified

Option C

Use a foreign key for an audit event that has no parent key.

Additional Explanation

This option is incorrect for the stated requirement.

Verified Correct Answer

Option D

DELIMITER // CREATE TRIGGER trg_customer_email AFTER UPDATE ON customers FOR EACH ROW BEGIN IF NOT (OLD.email <=> NEW.email) THEN INSERT INTO customer_audit(customer_id,old_email,new_email,changed_at) VALUES(NEW.id,OLD.email,NEW.email,NOW()); END IF; END // DELIMITER ;

Additional Explanation

Correct implementation. Prefer parameterized queries in application code, validate affected rows for UPDATE/DELETE, and use transactions for related writes.