Question 138 of 509
Comparing and Contrasting Data ConceptsmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is derived attribute, because total revenue is not stored directly in the database but is computed from existing stored data—specifically, by summing quantity multiplied by price for each customer. In database design, a derived attribute (sometimes called a computed attribute) is any value that can be calculated from other attributes, such as age from birth_date or, here, total_revenue from quantity and price. On the CompTIA Data+ DA0-001 exam, this concept tests your understanding of how data is logically modeled versus physically stored; a common trap is confusing a derived attribute with a stored attribute like customer_id, which is a key, not a calculation. To remember, think of the phrase “compute on demand”—if you can derive it from existing columns, it’s a derived attribute.

DA0-001 Comparing and Contrasting Data Concepts Practice Question

This DA0-001 practice question tests your understanding of comparing and contrasting data concepts. 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.

A retail company stores customer purchase history in a relational database. The database contains a table 'transactions' with columns: transaction_id, customer_id, product_id, quantity, price, and transaction_date. A data analyst needs to create a report that shows total revenue per customer for the last quarter. Which data concept describes the relationship between customer_id and total revenue?

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Derived attribute

Total revenue is calculated by summing (quantity * price) for each customer, making it a derived attribute because it is computed from existing stored data (quantity and price) rather than stored directly. In the context of the 'transactions' table, customer_id is a stored key, but total_revenue is not stored; it is derived via aggregation, which matches the definition of a derived attribute in database design.

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.

  • Foreign key

    Why it's wrong here

    Foreign key links tables, not derived values.

  • Composite attribute

    Why it's wrong here

    Composite attributes are made of sub-attributes, not derived.

  • Derived attribute

    Why this is correct

    Total revenue is calculated from other attributes, making it derived.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Atomic attribute

    Why it's wrong here

    customer_id is atomic, but total revenue is derived.

Common exam traps

Common exam trap: answer the scenario, not the keyword

CompTIA often tests the confusion between a derived attribute (computed from other attributes) and a foreign key (a referential constraint), leading candidates to incorrectly select 'foreign key' because customer_id appears in multiple tables.

Detailed technical explanation

How to think about this question

In relational database theory, derived attributes are often implemented as computed columns (e.g., SQL Server's PERSISTED or virtual computed columns) or calculated on the fly via queries using aggregate functions like SUM() with GROUP BY. Under the hood, the database engine may materialize the derived value for performance (stored derived attribute) or compute it each time (virtual derived attribute), but the key distinction is that the value is not independently stored in the table schema. For the DA0-001 exam, remember that derived attributes are not part of the physical table design but are logical constructs in reports or views.

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 DA0-001 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.

Related practice questions

Related DA0-001 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DA0-001 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DA0-001 question test?

Comparing and Contrasting Data Concepts — This question tests Comparing and Contrasting Data Concepts — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Derived attribute — Total revenue is calculated by summing (quantity * price) for each customer, making it a derived attribute because it is computed from existing stored data (quantity and price) rather than stored directly. In the context of the 'transactions' table, customer_id is a stored key, but total_revenue is not stored; it is derived via aggregation, which matches the definition of a derived attribute in database design.

What should I do if I get this DA0-001 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

This DA0-001 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 DA0-001 exam.