The answer is Widget, 2. This output comes from using COUNT with GROUP BY results in SQL, where the COUNT(*) function tallies the number of rows for each unique value in the specified column—here, Category. Because the table contains two entries labeled 'Widget' and one labeled 'Gadget', the query returns two rows: Widget with a count of 2, and Gadget with a count of 1. On the CompTIA ITF+ FC0-U61 exam, this concept tests your understanding of aggregate functions and how GROUP BY partitions data into distinct groups; a common trap is forgetting that GROUP BY collapses multiple rows into one per category, so you must mentally count each group’s rows. To remember, think “GROUP BY groups, COUNT counts each group’s rows.”
FC0-U61 Database Fundamentals Practice Question
This FC0-U61 practice question tests your understanding of database fundamentals. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
```
INSERT INTO Products (ProductID, ProductName, Price) VALUES (1, 'Widget', 10);
INSERT INTO Products (ProductID, ProductName, Price) VALUES (2, 'Gadget', 20);
INSERT INTO Products (ProductID, ProductName, Price) VALUES (3, 'Widget', 15);
SELECT ProductName, COUNT(*) FROM Products GROUP BY ProductName HAVING COUNT(*) > 1;
```
Refer to the exhibit. What is the output of the SELECT statement?
Refer to the exhibit.
```
INSERT INTO Products (ProductID, ProductName, Price) VALUES (1, 'Widget', 10);
INSERT INTO Products (ProductID, ProductName, Price) VALUES (2, 'Gadget', 20);
INSERT INTO Products (ProductID, ProductName, Price) VALUES (3, 'Widget', 15);
SELECT ProductName, COUNT(*) FROM Products GROUP BY ProductName HAVING COUNT(*) > 1;
```
A
Widget, 2
Why wrong: This is the correct data but the output format in a typical SQL client would show column names; however, the exact output includes both columns. Option D better matches the result set format.
B
Widget, 2
The GROUP BY groups by ProductName, and HAVING filters groups with count > 1, so only Widget (count 2) is returned.
C
Widget, 2; Gadget, 1
Why wrong: HAVING COUNT(*) > 1 filters out Gadget because its count is 1.
D
Widget, 2; Gadget, 1; Widget, 1
Why wrong: GROUP BY groups duplicates, so Widget appears once with count 2, and Gadget appears once with count 1, but HAVING filters out Gadget.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Widget, 2
The SELECT statement uses COUNT(*) with GROUP BY Category, which counts the number of rows per unique category value. The table has two rows with 'Widget' and one row with 'Gadget', so the output is two rows: Widget with count 2, and Gadget with count 1. Option B correctly lists both rows, matching the query's result.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Widget, 2
Why it's wrong here
This is the correct data but the output format in a typical SQL client would show column names; however, the exact output includes both columns. Option D better matches the result set format.
✓
Widget, 2
Why this is correct
The GROUP BY groups by ProductName, and HAVING filters groups with count > 1, so only Widget (count 2) is returned.
Related concept
Read the scenario before looking for a memorised answer.
✗
Widget, 2; Gadget, 1
Why it's wrong here
HAVING COUNT(*) > 1 filters out Gadget because its count is 1.
✗
Widget, 2; Gadget, 1; Widget, 1
Why it's wrong here
GROUP BY groups duplicates, so Widget appears once with count 2, and Gadget appears once with count 1, but HAVING filters out Gadget.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may forget that GROUP BY produces one row per unique group value, causing them to either omit groups with fewer rows or incorrectly include duplicate rows with partial counts.
Trap categories for this question
Command / output trap
This is the correct data but the output format in a typical SQL client would show column names; however, the exact output includes both columns. Option D better matches the result set format.
Detailed technical explanation
How to think about this question
The GROUP BY clause collapses rows with the same category value, and COUNT(*) counts the number of rows in each group. In SQL, COUNT(*) includes NULLs, but since Category is presumably NOT NULL here, it counts all rows per group. A common real-world scenario is generating summary reports, where forgetting that GROUP BY returns one row per unique group value leads to incorrect output.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Database Fundamentals — This question tests Database Fundamentals — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Widget, 2 — The SELECT statement uses COUNT(*) with GROUP BY Category, which counts the number of rows per unique category value. The table has two rows with 'Widget' and one row with 'Gadget', so the output is two rows: Widget with count 2, and Gadget with count 1. Option B correctly lists both rows, matching the query's result.
What should I do if I get this FC0-U61 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This FC0-U61 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the FC0-U61 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.