{!quote.Additional_Text__c}

Explanation:

1. Field Location:
The custom field Additional_Text__c exists on the Quote object (SBQQ__Quote__c).

2. HTML Template Syntax Rules:
In Salesforce CPQ HTML Templates, the Quote object is referenced using the quote merge field prefix.

The correct syntax is always:
{!quote.Field_API_Name__c}

3. Why This Works:
{!quote.Additional_Text__c} directly accesses the field from the Quote record.
No relationship notation (__r or __c) is needed because the field is on the Quote itself.

Why Not Other Options?

B: Incorrect prefix (Iquote__r is invalid; quote is the correct merge field name).

C: Unnecessary relationship syntax (SBQQ__Quote__r is used for cross-object fields, not fields on the Quote itself).

D: .Additional_Text__c cannot be accessed via SBQQ__Quote__c (this is the record ID, not the object reference).

Explanation:

What is an Amendment in Salesforce CPQ?

An Amendment allows modifications to an existing Contract or Subscription, typically for renewals, upsells, or changes to pricing/terms.

Key use cases include:

Updating quantities or discounts on existing products.
Adding new products while aligning with the original contract’s terms (e.g., co-termination).

Why Options A & C Are Correct?

A. Amendments support changing quantities and applying new discounts (e.g., renegotiating pricing).

C. Amendments allow adding new products while co-terminating (ending on the same date as the original contract).

Why Other Options Are Incorrect?

B. While quantities can change, maintaining the same discounts doesn’t require an Amendment (standard edits suffice).

D. Amendments cannot set a different End Date for new products; they must align with the original contract’s term.

Explanation:

Why This Works:

Evaluation Scope = Configurator
Ensures the Price Rule runs during product configuration (when Option A is selected), not just during quote calculation.

Configurator Evaluation Event = Edit
Triggers the rule in real time (as the user edits Option A), updating Option B’s Quantity immediately.

Why Other Options Fail:

A & C (Calculator Scope):
Rules run only during quote calculation (e.g., on Save), not in real-time configuration.

D (Configurator + Save):
"Save" delays the update until the user saves the bundle, breaking the real-time requirement.

Key Takeaway:
For real-time updates between Product Options, use:
✅ Configurator Scope + Edit Event.

Explanation:

UC sells in USD, GBP, and EUR. The Support SKU is only available in USD and EUR. All correct Pricebook Entries have been created for USD and EUR.

When adding a product to a quote:
- Salesforce CPQ checks whether there’s a Pricebook Entry for that product in the quote’s currency.
- If yes → product appears in Product Selection and can be added at the Pricebook Entry’s List Price.
- If no → product is unavailable in Product Selection and does not appear at all.

Therefore:

✅ USD → Product has a Pricebook Entry, visible in Product Selection, can be added at List Price.
✅ EUR → Product has a Pricebook Entry, visible in Product Selection, can be added at List Price.
🚫 GBP → No Pricebook Entry, product is unavailable in Product Selection.

This matches option C.

❌ Why Other Options Are Incorrect:

A. USD: Product is unavailable… EUR: Product is unavailable…
→ Incorrect. USD and EUR have valid pricebook entries, so the product should be available.

B. GBP: Added to Quote with 0 List Price.
→ Incorrect. If there’s no Pricebook Entry, the product cannot be added at all and does not appear in Product Selection.

D. Error presented to user…
→ Incorrect. Salesforce CPQ simply hides the product if it’s unavailable in the pricebook for the quote currency. No error is shown to the user.

✅ Example Scenario:

- GBP Quote → user searches “Support SKU” → product does not appear in the list.
- USD Quote → user searches “Support SKU” → product shows up with proper price.
- EUR Quote → user searches “Support SKU” → product shows up with proper price.

Explanation:

In Salesforce CPQ, Quote Terms are used to insert standardized legal or financial text into the quote documents. To prevent non-admin users from modifying a specific Quote Term, the best practice is to use the Locked checkbox on the Quote Term record.

✅ When Locked = TRUE:
The Quote Term becomes read-only for non-admin users.
Only users with the Modify All Data permission (typically admins) can edit or delete the term.
This is the intended method for restricting edit access to Quote Terms.

❌ Why the other options are incorrect:

A. Read-Only checkbox:
No such standard checkbox exists on Quote Term records.

B. On the User Profile, make the object Read-Only:
Overly restrictive — this would prevent users from seeing or interacting with any Quote Terms, not just specific ones.

C. Make the Object Read-Only:
Same issue as B — applies broadly to the entire object, not specific records.