When developing a report, which two should be defined for a JOIN query?

Question

Options

• Aa reference to two queries
• Bonly cached results
• Can expression editor
• Dan intersection of two queries
• Ea relationship defining cardinality

• A
  79% (22)
• B
  11% (3)
• C
  7% (2)
• E
  4% (1)

Explanation

A JOIN query in a report requires two source queries to combine (A) and an intersection point-the common field(s) that defines how those queries link together (D). Think of D as the "where they meet": without specifying the shared column(s), the report engine has no basis for merging the data.

The distractors fail because: B (cached results) is a performance/storage concern, not a structural requirement for defining a JOIN; C (expression editor) is a tool for calculated fields or custom formulas, not for configuring query relationships; E (cardinality) describes how many records match (one-to-one, one-to-many), which is a property of a relationship but is not itself what you define when setting up a JOIN query in a report builder context.

Memory tip: Think "JOIN = 2 + connect" - you need 2 queries (A) and the connection point between them, i.e., the intersection (D). If you remember those two elements, you've got the JOIN defined.

No community discussion yet for this question.