Key Takeaways
In this sorted numeric table, 200 must return B and 250 must remain unmatched. Use FALSE explicitly in VLOOKUP and check XLOOKUP’s mode where available. The incorrect draft and reference answer below are original teaching material, not a recorded model test.
- For the numeric-ID example, 200 must return B and 250 must remain unmatched rather than borrowing a neighboring ID.Read the supporting section: Define identity before asking for a formula
- Set FALSE explicitly in VLOOKUP; a returned value does not prove that the identity match is correct.Read the supporting section: Keep cases that distinguish the behaviors
- Check known and missing IDs in the actual workbook; the article’s incorrect AI draft is teaching material.Read the supporting section: Verify in the actual workbook
In this article
Define identity before asking for a formula
Look up the numeric ID in D2 against A2:B4 and return its owner. IDs are identities, not price bands or interval thresholds: only equal IDs qualify. The table is deliberately sorted to remove ordering as a competing explanation.
The exercise uses numeric 100, 200 and 300, without leading zeros or numeric text. If a real system treats 00100 as a distinct string, preserve that identity rather than coercing it to 100 just to make a formula work.
| ID | Owner |
|---|---|
| 100 | A |
| 200 | B |
| 300 | C |
A2:B4 contains numeric IDs and owners: 100→A, 200→B, 300→C. The query is in D2.
Require exact equality. Keep an unmatched state; never borrow a nearby ID.
Write an Excel formula, explain the match argument and predict results for D2=200, 250 and 50.
Do not erase all errors into blanks. Explain why duplicate IDs need a separate check.A wrong result need not produce an Excel error
Microsoft’s VLOOKUP reference documents approximate matching when range_lookup is omitted and sorting for TRUE mode. In this exercise, =VLOOKUP(D2,$A$2:$B$4,2) can return B from the 200 row when D2 is 250. That is meaningful for a band lookup, but violates this task’s identity rule.
Testing only D2=200 is insufficient: the flawed formula also returns B there. Query 250 distinguishes exact equality from the nearby lower entry and exposes the otherwise plausible mistake.
A believable incorrect draft
=VLOOKUP(D2,$A$2:$B$4,2) D2=250 → B, so B owns this ID.
=VLOOKUP(D2,$A$2:$B$4,2,FALSE) D2=250 → #N/A; no equal ID exists, so review it.
Keep cases that distinguish the behaviors
With explicit FALSE, 200 returns B, while 250 and 50 return #N/A. Do not blanket-replace every error with an empty cell that downstream work may interpret as merely unfilled. If a readable label is required, IFNA can handle the unmatched case while a separate exception count remains visible.
Microsoft’s XLOOKUP documentation identifies exact matching as its default and notes that Excel 2016 and 2019 do not provide it. Where supported, =XLOOKUP(D2,$A$2:$A$4,$B$2:$B$4,"Not found",0) makes mode 0 explicit. A newer function name does not validate compatibility or data quality.
| D2 | VLOOKUP without fourth argument | VLOOKUP(...,FALSE) | XLOOKUP(...,0) |
|---|---|---|---|
| 200 | B | B | B |
| 250 | B (wrong identity) | #N/A | Not found |
| 50 | #N/A | #N/A | Not found |
Verify in the actual workbook
Copy the exercise into a blank workbook and confirm range, column order and numeric types. Enter queries and formulas separately and compare each result with the reference. Record Excel version and regional syntax; adapt separators where necessary without changing field meaning. These are reproducible expectations, not a claim of execution in your workbook.
Then append 200→D and extend the range. Exact matching establishes equality, not uniqueness: a lookup may return the first match while hiding a conflict. Count rows per ID and resolve duplicates under an explicit rule rather than treating return order as a business decision.
The stable-ID and name-collision guide explains identity keys. The AI spreadsheet formula acceptance guide helps preserve inputs, ranges and expectations.
Evidence before handing off the formula
- Existing, internal-gap and below-range queries match the reference.
- Range growth, types and application compatibility have been checked.
- Unmatched IDs, other errors and duplicates have not all become blanks.
- Actual workbook output is recorded separately from AI explanations and hand calculations.


