Salesforce AP-223 Exam Questions

Requirement:

Set Legal Entity on Order Product and OP Consumption Schedule in a scalable way.

Runs before insert, so no second update transaction is needed.

Scalable (bulk-safe, low CPU, no recursion).

Modern Salesforce best practice for field population.

Works consistently across:

Order Products

Usage/Consumption Schedules

Why D. Before-Save Flow is correctWhy not the others?Option

Why Incorrect

A . Workflow Rule

Deprecated, not scalable, cannot run before-save.

B . Custom Setting

Storage mechanism, not automation logic.

C . QCP

Only affects Quote stage, not Order Products or Consumption Schedules AFTER order creation.

Thus **D is the correct, scalable, and recommended pattern.

Salesforce Billing's Hold Billing field on Order Product works exactly as follows:

When Hold Billing = Yes, Salesforce Billing does not generate invoice lines for that Order Product.

Once the user sets Hold Billing back to No, Billing:

Calculates the missed invoice periods

Creates catch-up invoice lines so billing is not lost

Correct Behavior (per Documentation)This means:

Invoicing is suspended

Catch-up invoice lines are created for the entire period Hold Billing was active

Thus, C is the correct and documented behavior.

Why the other answers are incorrectOption

Description

Why Incorrect

A

Prevents invoice document generation and emails

Misleading: the function specifically stops invoice line creation for the order product; it does not manage email notifications.

B

Hold Billing auto-resets on activation

False. Hold Billing is a manual field and does not auto-clear.

D

Only invoices after Hold Billing is set to No are created

Incorrect---Billing creates catch-up invoices for missed time.

Thus, C is completely aligned with Salesforce Billing behavior.

The requirement:

One Order Product must invoice 2 months of charges on the next invoice, without affecting the other 4 Order Products.

To do this, you must tell Billing to:

Skip 1 billing cycle

Jump ahead to a future billing date

Without impacting other Order Products

Without modifying invoicing schedule globally

The correct way is to set:

Override Next Billing Date This forces the next invoice line to include charges up to the new date, resulting in multiple periods billed together.

Why others are wrong:Option

Explanation

B --- Hold Billing

Pauses billing entirely; does NOT create multi-month invoices.

C --- Target Date

Controls invoice run date, not multi-period billing.

D --- Bill Through Date Override

Controls end date of a prorated period, not the number of periods billed.

E --- Bill Now

Generates an immediate invoice but still only bills 1 period unless dates are overridden.

Thus A (Override Next Billing Date) is correct.

Scenario SummaryUniversal Containers sells a bundle ''Corporate IT Solutions.''

Inside it is a product option: Hardware Firewall.

Requirement:

If the customer previously purchased that Hardware Firewall (historical purchase),

Then hide the product option inside the bundle during configuration.

This is a Configuration Rule

Using Selection/Filter logic to hide options

The rule must trigger as soon as the bundle loads, because the product option must be hidden before the user interacts with the bundle.

What type of Product Rule?Which Evaluation Event is Correct?Salesforce CPQ Product Rule Evaluation Events:

Event

When it Fires

Typical Use

Load

When the configuration page loads the first time

Hide/show options, preselect options, set initial values

Edit

On any user modification

Rerun rules based on changes

Load and Edit

Both events above

When both initial setup and change handling are required

Save

When the quote line editor is saved

Validation rules that block save

We need the product option to be hidden immediately when configuring the bundle.

It is not dependent on user edits.

It uses historical purchase data (Opportunity Product / Asset / Subscriptions).

In this requirementTherefore, the rule should fire at initial load only, not waiting for user interaction.

Always not a valid Product Rule Event type in CPQ.

Save too late; user would see the option before it's hidden.

Load and Edit unnecessary; we do not need edits to trigger this rule.

Edit would fail because hiding must occur before user interaction.

Why Not the Others?Salesforce CPQ Documentation AlignmentCPQ Product Rules documentation states:

Use Load when you want the rule to evaluate immediately when the configurator opens, typically for hiding, filtering, or preselecting options.

This matches the required behavior perfectly.