Explanation:

Let’s walk through the scenario:
“UC allows clients to negotiate a discount for Product A until a specified date up to contract activation.”

This means:

The discount is specific to Product A → you must relate it to a Product.
It’s valid only until a specific date → need an Expiration Date.
It’s a discount value → need the Discount field.

Hence the three required fields:

✅ A. Product

→ Correct
Contracted Price records are linked to a Product so CPQ knows which product to apply the negotiated price or discount to.
Without the Product field, the system won’t know which product receives the special price.

❌ B. Contract

→ Incorrect
Contracted Price records are not directly tied to a Contract record.
They relate to the Account, Product, or Product Family, but not directly to a specific Contract.

✅ C. Expiration Date

→ Correct
The requirement states “until a specified date.”
The Expiration Date on the Contracted Price determines when this special pricing stops being applied.
After expiration, the system reverts to standard pricing.

✅ D. Discount

→ Correct
Since this is about a negotiated discount, the Discount field must be filled in to define the % discount for the product.

❌ E. Effective Date

→ Incorrect (not required here)
Effective Date defines when the Contracted Price starts being applied.
The question only says, “until a specified date,” so the Expiration Date is mandatory.
Effective Date could be used, but it’s not strictly required unless the discount is future-dated.

So, the three essential fields to meet the requirement are:
✅ Product → defines which product the discount applies to.
✅ Expiration Date → controls when the discount ends.
✅ Discount → sets the negotiated % off the price.