Multiple choice technology databases

For performance, you denormalize your database design and create some redundant columns. Referring to the scenario above, what RDBMS construct can you use to automatically prevent the repeated columns from getting out of sync?

  1. Cursors

  2. Constraints

  3. Views

  4. Stored procedures

  5. Trigger
Reveal answer Fill a bubble to check yourself
E Correct answer
Explanation

Triggers automatically execute in response to data changes (INSERT/UPDATE/DELETE), making them ideal for synchronizing denormalized data across multiple tables to prevent inconsistent redundant values.

AI explanation

Correct answer: Trigger. When you denormalize a schema and store redundant/duplicate copies of a column across tables, a trigger (fired on INSERT/UPDATE/DELETE) can automatically propagate changes to keep the copies in sync. Cursors and stored procedures only run when explicitly invoked, constraints just restrict/validate values rather than propagate them, and views are just virtual queries over existing data — none of these automatically fire on data changes the way a trigger does.

Keep practicing — related questions