An application's account features are register, view profile, change email address and close account, where closing removes the user's row. Which SQL statements map to these four actions, in that order?
Select an answer to reveal the explanation.
Short Explanation
CRUD is Create, Read, Update, Delete, and in SQL that's INSERT, SELECT, UPDATE, DELETE. Here's the trap: CREATE, ALTER and DROP sound like the same verbs, but they reshape tables, not rows. If you DROP to close one account, you just closed everybody's.
Full Explanation
The CRUD principle describes the four basic operations an application performs on records. In SQL, they map to data manipulation and query statements that act on rows: INSERT creates a new row when a user registers, SELECT reads the row to display a profile, UPDATE changes a column value such as the email address, and DELETE removes the user's row when the account is closed. Mapping registration and account closure to CREATE and DROP confuses CRUD's vocabulary with Data Definition Language: CREATE builds a new object such as a table, and DROP removes the entire object along with every row in it, so closing one account this way would destroy all accounts. ALTER also belongs to DDL and changes a table's structure, such as a column's type, rather than a single user's email value. TRUNCATE removes all rows from a table at once without a row-level filter, so it cannot close one specific account. Exam caveat: CRUD is an application-level concept, and some designs implement account closure as a soft delete, an UPDATE that sets a status flag, but the stem specifies removing the row. Operational check: trace each feature in the application's SQL log and confirm it issues the expected row-level statement with a WHERE clause on the user's key for reads, updates and deletes.