Which expression is used to define the PricingGroup based on ListPrice thresholds?

Which expression is used to define the PricingGroup based on ListPrice thresholds?

• A. CASE
• B. COALESCE
• C. IIF
• D. SET

Answer: (A)

Using a multi-branch conditional expression lets you map numeric ranges to labeled groups in a clear, maintainable way. A CASE expression is designed for this exact need: you list the thresholds as WHEN conditions and assign the corresponding label with THEN, finishing with ELSE for anything that doesn’t fit a prior range. This lets you define PricingGroup directly from ListPrice by stepping through the price ranges in order. Example: CASE WHEN ListPrice < 100 THEN 'Budget' WHEN ListPrice < 500 THEN 'Standard' WHEN ListPrice < 1000 THEN 'Premium' ELSE 'Luxury' END AS PricingGroup. COALESCE isn’t about categorizing by ranges; it selects the first non-null value. IIF can handle simple two-way decisions and becomes messy with many thresholds. SET is for assigning variables or setting options, not for deriving a categorized field. So CASE best fits the need.

Using a multi-branch conditional expression lets you map numeric ranges to labeled groups in a clear, maintainable way. A CASE expression is designed for this exact need: you list the thresholds as WHEN conditions and assign the corresponding label with THEN, finishing with ELSE for anything that doesn’t fit a prior range. This lets you define PricingGroup directly from ListPrice by stepping through the price ranges in order.

Example: CASE WHEN ListPrice < 100 THEN 'Budget' WHEN ListPrice < 500 THEN 'Standard' WHEN ListPrice < 1000 THEN 'Premium' ELSE 'Luxury' END AS PricingGroup.

COALESCE isn’t about categorizing by ranges; it selects the first non-null value. IIF can handle simple two-way decisions and becomes messy with many thresholds. SET is for assigning variables or setting options, not for deriving a categorized field. So CASE best fits the need.