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.

• ✓

  SELECT name, price FROM Products WHERE price > 50;

  Why this is correct

  SELECT name, price FROM Products WHERE price > 50; projects only the two required columns and applies the greater-than filter on price, returning exactly the product names and prices requested. The WHERE clause enforces the price constraint.

• ✗

  GET name, price FROM Products WHERE price > 50;

  Why it's wrong here

  GET is not a valid SQL keyword.

• ✗

  SELECT name, price FROM Products;

  Why it's wrong here

  Omitting the WHERE clause returns every row, so products priced at 50 or below are included, violating the filter requirement. It is tempting because SELECT with a column list is the correct pattern for retrieving specific fields from a table; it would be right if all products were wanted without a price condition.

• ✗

  SELECT * FROM Products WHERE price > 50;

  Why it's wrong here

  SELECT * returns every column, including ones the user did not request, so it fails the requirement to retrieve only product names and prices. It is tempting because SELECT * is the standard shorthand for fetching all columns from a table, and would be correct if the whole row were genuinely needed.