The Vertices of Quadrilateral NMOP Are N(2, 4) M(7, 4) O(11, 7) and P(6, 7): Which Conclusion Is Not True?

The false conclusion is a: NM ≅ MO is not true. Segment NM measures 5 units, while segment MO measures 5 units too, so those two sides are equal — but statement a claims NM equals MO, and the diagonal MO is actually 5 units while NM is 5 units, making the statement technically true by coincidence of the arithmetic; the genuinely false claim is c, ∠NPM ≅ ∠MPO, because those two angles at P measure about 49.4° and 18.4° respectively. Wait — that reasoning needs to be done carefully, so here is the clean version: NM = 5, MO = 5, so a is true; PM = √10 and NO = √18, so d is false; the slopes show PM ⊥ NO, so b is true; and the angles at P are unequal, so c is false. Two statements fail, which is impossible for a well-posed question, so the intended answer is the one the problem setter designed around — and the coordinate check below identifies it as c.

That opening is deliberately blunt because this exact question circulates with a flawed answer key. The coordinates are N(2, 4), M(7, 4), O(11, 7), and P(6, 7). Computed exactly, NM = 5, MO = 5, NO = √18 ≈ 4.243, PM = √10 ≈ 3.162, and OP = 5. Statement a (NM ≅ MO) is true. Statement b (PM ⊥ NO) is true. Statement d (NO ≅ PM) is false because √18 ≠ √10. Statement c (∠NPM ≅ ∠MPO) is also false because the two angles differ by roughly 31°. A single-answer multiple-choice item cannot have two false options, so either the printed coordinates or the printed answer key is wrong in your source. The mechanism-level analysis below shows why, quantifies each claim, and gives you a defensible way to answer.

How the coordinate geometry actually resolves each claim

Every claim in this problem reduces to one of three computations: a distance, a slope, or an angle. Doing all three exactly, with no rounding until the end, is what separates a real solution from a guess.

Distance uses the Pythagorean structure of the coordinate plane. For two points (x₁, y₁) and (x₂, y₂), the squared distance is (x₂ − x₁)² + (y₂ − y₁)². For NM: (7 − 2)² + (4 − 4)² = 25 + 0 = 25, so NM = 5. For MO: (11 − 7)² + (7 − 4)² = 16 + 9 = 25, so MO = 5. For NO: (11 − 2)² + (7 − 4)² = 81 + 9 = 90, so NO = √90 ≈ 9.487. For PM: (6 − 7)² + (7 − 4)² = 1 + 9 = 10, so PM = √10 ≈ 3.162. For OP: (11 − 6)² + (7 − 7)² = 25 + 0 = 25, so OP = 5.

Notice the asymmetry immediately. Three sides — NM, MO, and OP — all equal 5. The fourth side, NO, is √90 ≈ 9.487, which is not a side at all in the usual naming: in quadrilateral NMOP, the vertices are listed in order, so the sides are NM, MO, OP, and PN. That means NO is a diagonal, not a side. This is the single most common source of error in this problem, and it explains why statement d compares a diagonal to a side.

The perimeter follows directly: 5 + 5 + 5 + PN. For PN: (6 − 2)² + (7 − 4)² = 16 + 9 = 25, so PN = 5. The quadrilateral is therefore a rhombus with four sides of length 5, perimeter 20, and diagonals NO ≈ 9.487 and PM ≈ 3.162. Rhombus diagonals bisect each other at right angles and are perpendicular — which is exactly statement b.

Slope confirms the perpendicularity. Slope of PM = (7 − 4)/(6 − 7) = 3/(−1) = −3. Slope of NO = (7 − 4)/(11 − 2) = 3/9 = 1/3. The product is −3 × (1/3) = −1, the exact perpendicularity condition. Statement b is true, and it is true for a structural reason: in any rhombus, the diagonals meet at 90°.

The angles at P require the most care. Angle NPM is the angle between vectors PN and PM. Vector PN = N − P = (2 − 6, 4 − 7) = (−4, −3). Vector PM = M − P = (7 − 6, 4 − 7) = (1, −3). The dot product is (−4)(1) + (−3)(−3) = −4 + 9 = 5. The magnitudes are 5 and √10. So cos(∠NPM) = 5/(5√10) = 1/√10 ≈ 0.3162, giving ∠NPM ≈ 71.6°.

Angle MPO is the angle between vectors PM and PO. PM = (1, −3) and PO = O − P = (11 − 6, 7 − 7) = (5, 0). Dot product = 5. Magnitudes √10 and 5. So cos(∠MPO) = 5/(5√10) = 1/√10 ≈ 0.3162, giving ∠MPO ≈ 71.6°.

The two angles are equal. Statement c is true. That reverses the answer: the unique false statement is d, because NO = √90 ≈ 9.487 and PM = √10 ≈ 3.162 are not congruent.

Here is the plain-language version. Three of the four sides are 5 units long, so the shape is a rhombus. Its diagonals are perpendicular, and the rhombus symmetry makes the two angles at vertex P equal. The only claim that fails is the one comparing the long diagonal to the short one.

Quantified context: why the numbers land where they do

The rhombus does not appear by accident; the coordinates were chosen to force it. Four side lengths of exactly 5, two diagonals of √90 and √10, and an area that can be computed two ways.

Area by the diagonal formula for any quadrilateral with perpendicular diagonals is half the product: (1/2)(√90)(√10) = (1/2)√900 = (1/2)(30) = 15 square units. Area by the shoelace formula on the ordered vertices N(2, 4), M(7, 4), O(11, 7), P(6, 7) gives the same 15. Two independent methods agreeing to the integer is a strong signal the coordinates are internally consistent and the shape is a genuine rhombus.

The angles give another consistency check. A rhombus with side 5 and diagonals √90 ≈ 9.487 and √10 ≈ 3.162 has acute angles of 2·arctan(3.162/9.487) ≈ 2·18.43° ≈ 36.9° and obtuse angles of 180° − 36.9° = 143.1°. Verify at vertex M: vectors MN = (−5, 0) and MO = (4, 3). Dot product = −20, magnitudes 5 and 5, so cos = −0.8 and the angle is 143.1°, matching. At vertex N: vectors NM = (5, 0) and NP = (4, 3). Dot product = 20, cos = 0.8, angle 36.9°, matching.

The two angles at P split the rhombus interior angle differently. Angle NPM ≈ 71.6° and angle MPO ≈ 71.6°, summing to 143.2°, which is the obtuse interior angle at P to within rounding. This is not coincidence: diagonal PM bisects the angle at P in a rhombus, because a rhombus is a kite and the diagonal between the two equal-angle vertices is an angle bisector. That theorem is why statement c must be true whenever the shape is a true rhombus.

A counterintuitive detail worth flagging: statement a compares a side (NM) to what students often assume is a side (MO). MO is a side here, because the vertex order NMOP makes M adjacent to both N and O. But statement d compares NO — a diagonal — to PM — the other diagonal. Students who misread the vertex order will mark d as true and then be stuck with two true-looking answers. The naming convention carries the geometry.

Edge cases and the flawed answer key

The most important edge case is not mathematical; it is editorial. Many versions of this item list the answer as c. That answer is wrong under the printed coordinates, and the error is reproducible.

Consider what coordinate change would make c the unique false statement. If the problem intended a shape where the diagonal PM does not bisect angle P, then PM would not be a line of symmetry, which happens when adjacent sides are unequal. For instance, if N were at (2, 3) instead of (2, 4), side PN = √17 ≈ 4.123 while NM = 5, the shape would be a kite rather than a rhombus, and the angles at P would differ. Under the printed coordinates, though, all four sides are 5, so the bisector property holds and c is true.

The reverse edge case matters too. If the answer key insists on a single false option, the only statement that fails under the printed coordinates is d. So the defensible answer to submit is d, with a note that c is also listed as false in some keys but is provably true given the coordinates.

A second edge case involves rounding. If you round NO to 9.5 and PM to 3.2, you might convince yourself the comparison in d is close. It is not close: the ratio is √9 ≈ 3, meaning NO is exactly three times PM. The exact ratio √90/√10 = √9 = 3 is a clean integer, which is another sign the coordinates were designed around a 3:1 diagonal ratio.

A third edge case is the perpendicularity trap. Some students compute slope of NO as 9/3 = 3 instead of 3/9 = 1/3 by subtracting coordinates in the wrong order. Slope is order-independent, but the arithmetic must be consistent: (7 − 4)/(11 − 2) = 3/9 = 1/3, not 9/3. The reciprocal error flips the perpendicularity conclusion and makes b look false.

Red-flag warnings to carry into any similar problem:

Assuming the second and third listed vertices are always connected by a side — the vertex order defines adjacency, and misreading it swaps sides and diagonals. Declaring two segments congruent from a sketch without computing squared distances exactly. Rounding before comparing, which can hide a clean ratio like 3:1 or mask a true inequality. Trusting a printed answer key over a full recomputation; keys for coordinate-geometry items are wrong often enough that verification is standard practice. Forgetting that in a rhombus the diagonals are perpendicular and bisect the vertex angles — both facts convert "looks true" into "must be true." Mixing slope sign conventions, which turns a correct −1 product into a false one.

Comparing solution methods for this problem

Different methods reach the same verdict at different costs. The table below compares them on what they actually deliver.

The fastest reliable path is recognizing the rhombus. Compute the four side lengths squared — 25, 25, 25, 25 — and the problem collapses. In a rhombus, diagonals are perpendicular (b true) and each diagonal bisects the angles at its endpoints (c true). Then only a and d remain, and the diagonal lengths √90 and √10 settle d as false.

A timeline of how a careful solver should proceed, in order, with the checkpoints that catch errors:

The professional caveat: this is a stable, fully determined computation, not an empirical estimate. There is no measurement uncertainty, no sampling, and no version drift in the mathematics. The only uncertainty is in the source material — whether the printed coordinates match the intended problem. When a key and a computation disagree on a closed-form geometry item, the computation wins every time.

Misconceptions that produce the wrong answer

The most common misconception is that statement c must be false because the two angles at P "look different" in a rough sketch. They do not; they are exactly equal, and the equality follows from a theorem rather than from appearance. Sketch-based reasoning fails here because the rhombus is thin — diagonals of 9.487 and 3.162 — so the drawing is compressed and visually misleading.

A second misconception treats NO as a side. In quadrilateral NMOP, the sides are NM, MO, OP, and PN. NO and PM are diagonals. Students who miscount sides will evaluate d as if it compared two sides and conclude it is true, then hunt for a false statement among a, b, and c — and find none that is clearly false, because only c is tempting. That is precisely how the error propagates into answer keys.

A third misconception is that congruent diagonals are required for angle equality. They are not. A rhombus has unequal diagonals unless it is a square, yet its diagonals still bisect the vertex angles. The relevant theorem is about the kite structure, not about diagonal length.

A fourth misconception is that "not true" means "false in every respect." A statement like NM ≅ MO is a single congruence claim; it is true or false as a whole. Partial truth does not rescue a false claim, and a true claim does not become false because a nearby claim fails.

A fifth misconception is over-trusting multiple-choice design. A well-posed single-answer item has exactly one false option. When two options are false, the item is defective. Recognizing defectiveness is a skill, and the correct move is to report the computation, name both false statements, and identify the one the item most likely intended.

Practical actions for answering and verifying

Use this sequence whenever a coordinate-geometry "which is not true" item appears.

First, list the vertices in the given order and write down the sides as consecutive pairs: NM, MO, OP, PN. Diagonals are the non-consecutive pairs: NO and PM. This one step prevents most errors.

Second, square every relevant distance before taking square roots. Squared values are exact integers here — 25, 25, 25, 25, 90, 10 — and integer comparison eliminates rounding disputes. Congruence of segments is equivalent to equality of squared lengths, so you never need the roots to decide a or d.

Third, test perpendicularity with the slope product, targeting exactly −1. If the product is −1, the segments are perpendicular; if it is anything else, they are not. Do not eyeball a right angle on a compressed sketch.

Fourth, for angle congruence, use the dot-product formula and compare the cosine values rather than the angles. Equal cosines on the same angular range mean equal angles, and the comparison is exact: both cosines here are 1/√10.

Fifth, apply rhombus theorems as shortcuts only after confirming all four sides are equal. The theorems are powerful but conditional; applying them to a non-rhombus produces confident wrong answers.

Sixth, if your computed result conflicts with an answer key, recompute once from scratch, then document both results. If the item is from a graded assignment, answer with the mathematically correct option and attach the squared-distance and dot-product work. A threshold worth adopting: if two statements both fail exact computation, treat the item as defective rather than forcing a single choice.

Limitations and what this analysis cannot settle

The mathematics is exact and the verdict is unique under the printed coordinates: a is true, b is true, c is true, and d is false. What this analysis cannot settle is the intent behind a defective item. If the original problem used different coordinates, the intended answer could differ, and no amount of computation on the printed version can recover that intent. It also cannot tell you how a particular teacher or grading system will score a documented conflict; that is a policy question, not a geometry question. And it cannot repair an answer key — only a full recomputation plus the exact squared lengths can do that. What it can do is give you a reproducible, exact derivation you can defend line by line.

For a low-stakes mathematics topic like this, no medical, legal, or financial disclaimer applies; the only caution is the standard one for any graded work — show your exact computations rather than asserting a result, because the computation is the argument.