New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce AP-223 Exam - Topic 2 Question 3 Discussion

Actual exam question for Salesforce's AP-223 exam
Question #: 3
Topic #: 2
[All AP-223 Questions]

Universal Containers sell a product bundle named ''Corporate IT Solutions''. One of the product options inside this bundle is named Hardware Firewall Universal Containers has a requirement where if the customer has purchased a hardware firewall in the past, the hardware firewall product option should be hidden while configuring the bundle.

The CPQ admin has created a product rule to handle this requirement. What should the evaluation event of the product rule be set to?

Show Suggested Answer Hide Answer
Suggested Answer: D

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.


Contribute your Thoughts:

0/2000 characters
Shawn
7 days ago
B) Save. The product rule should be evaluated when the customer is saving the bundle configuration.
upvoted 0 times
...
Junita
13 days ago
C) Load and Edit. The requirement mentions configuring the bundle, so the evaluation event should be set to Load and Edit.
upvoted 0 times
...
Jennie
18 days ago
D) Load. This seems like the correct choice to hide the hardware firewall option if the customer has purchased it before.
upvoted 0 times
...
Val
23 days ago
I feel like "Always" is too broad for this scenario. It seems like we only need to evaluate when the bundle is loaded.
upvoted 0 times
...
Caitlin
28 days ago
This reminds me of a practice question where we had to hide options based on previous selections. I think "Load and Edit" might be relevant here, but I could be wrong.
upvoted 0 times
...
Skye
1 month ago
I'm not entirely sure, but I remember something about "Save" being used for rules that need to validate after changes.
upvoted 0 times
...
Wade
1 month ago
I think the evaluation event should be set to "Load" because it needs to check the customer's previous purchases when they first load the bundle.
upvoted 0 times
...
Desmond
1 month ago
This seems straightforward to me. The requirement is to hide the hardware firewall option if the customer has purchased it before, so the evaluation event should be set to Load and Edit. That way, the rule will be checked as the customer is configuring the bundle.
upvoted 0 times
...
Sarina
2 months ago
I'm a bit confused here. The question doesn't specify when the customer's past purchase history is checked. Could it be that the evaluation event should be set to Load, to check the customer's history as soon as the bundle is loaded? I'm not sure, but I'll give that a try.
upvoted 0 times
...
Rana
2 months ago
Okay, let me think this through. The requirement is to hide the hardware firewall option if the customer has purchased it before. So the rule needs to be evaluated when the bundle is being loaded and edited, not just when it's being saved. I'm going with C) Load and Edit.
upvoted 0 times
...
Johnathon
2 months ago
Hmm, I'm not sure about this one. The question mentions a product rule, so I'm thinking the evaluation event might need to be set to Save, to ensure the rule is applied when the customer is finalizing their purchase.
upvoted 0 times
...
Dana
2 months ago
I think the evaluation event should be set to Load and Edit, since the requirement is to hide the hardware firewall option if the customer has purchased it in the past. This would ensure the rule is evaluated when the bundle is being configured.
upvoted 0 times
Tommy
2 months ago
I agree, Load and Edit makes sense.
upvoted 0 times
...
...
Cammy
2 months ago
I think it should be D) Load. It makes sense to check when loading the bundle.
upvoted 0 times
...

Save Cancel