Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Learn Challenge: Query Testing | Query Engine Basics
Practice
Projects
Quizzes & Challenges
Quizzes
Challenges
/
BigQuery Fundamentals

bookChallenge: Query Testing

Swipe to show menu

Validate calculated totals in a query by checking whether the recorded total amount matches what it should be based on quantity and unit price. The focus is on identifying incorrect records by recalculating the expected total and filtering for mismatches. The end goal is to return only the rows where the stored total is wrong, helping ensure data accuracy in transactional datasets.

The query is expected to return three specific rows, which represent records where the totals do not align correctly.

The core validation logic is:

QuantityΓ—UnitΒ Price=CorrectΒ Total\text{Quantity} Γ— \text{Unit Price} = \text{Correct Total}

Compare this calculated value against the existing Total Amount column.

A new calculated column is created to represent the correct total (quantity multiplied by unit price). This makes the comparison explicit and easier to reason about.

The query then filters results to include only rows where:

Total Amount≠Quantity×Unit Price\text{Total Amount} ≠ \text{Quantity} × \text{Unit Price}

This approach allows you to:

  • Identify incorrect or inconsistent transactional records;
  • Debug pricing or data-entry issues;
  • Validate business logic directly within SQL rather than externally.

The challenge being solved is not about aggregations, but about row-level validation, ensuring each transaction is internally consistent.

Everything was clear?

How can we improve it?

Thanks for your feedback!

SectionΒ 2. ChapterΒ 8

Ask AI

expand

Ask AI

ChatGPT

Ask anything or try one of the suggested questions to begin our chat

SectionΒ 2. ChapterΒ 8
some-alt