FC0-U71 Data and Database Fundamentals Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  ADD INTO Customers VALUES (1, 'John', 'john@example.com');

  Why it's wrong here

  ADD is not a SQL data-manipulation keyword; the statement must begin with INSERT INTO, so this fails at parse time. It tempts because ADD sounds like appending a record, and would be correct in DDL contexts such as ALTER TABLE ... ADD COLUMN, not row insertion.

• ✗

  INSERT Customers VALUES (1, 'John', 'john@example.com');

  Why it's wrong here

  Missing INTO keyword; syntax incorrect.

• ✗

  UPDATE Customers SET Name='John' WHERE ID=1;

  Why it's wrong here

  UPDATE modifies existing rows matched by a WHERE clause; it cannot create the new record the employee needs. It tempts because UPDATE is the right statement when changing an existing customer's stored details, such as correcting a name against a known ID. Here no row exists yet, so INSERT INTO Customers (ID, Name, Email) VALUES (...) is required.

• ✓

  INSERT INTO Customers VALUES (1, 'John', 'john@example.com');

  Why this is correct

  INSERT INTO with VALUES adds a single row to the named table, supplying the three column values in the table's declared order (ID, Name, Email). This satisfies the requirement to add one new customer record, since no existing rows are modified or selected.