Salesforce AP-223 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: When a Salesforce CPQ user logs into production for the first time, CPQ requires running the Post- Install Script. This script: Creates default settings Ensures CPQ-managed fields are initialized Grants required permissions Creates default Primary Quote logic metadata Updates field values such as IsPrimary, quote calculation settings, etc. Why the issue happened The customer implemented automation that automatically sets a new quote as Primary at creation. If a user has not executed the CPQ Post-Install Script on their first login, then Salesforce CPQ has not yet initialized several objects and fields that are required for the Primary Quote creation process. Therefore, the “first time users tried to create quotes” → they encountered errors, because: Their user-specific CPQ installation metadata was not initialized CPQ could not run its internal logic that depends on Primary Quote setup Salesforce’s installation documentation explicitly states: Each CPQ user must run the Post-Install Script after first login, or they may encounter errors when creating quotes, setting a quote primary, or performing calculations. Thus the correct answer is A, and it is consistent with CPQ installation best practices.

Explanation: Scenario Summary Universal 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 requirement Therefore, 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 Alignment CPQ 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.

Explanation: In every Salesforce CPQ implementation, Product Bundles are one of the core configuration capabilities that must be discussed during scoping and discovery―even if the customer does not initially think they need them. ✔ Why the correct answer is BB. Yes, bundle configuration should be introduced and it's up to the customer to decide whether they need it or not. This aligns fully with Salesforce CPQ implementation best practices, discovery methodology, and the guidance in CPQ documentation and study resources. Why bundles must be discussed in scoping Salesforce CPQ Bundles are used to solve many common quoting problems: Grouping products together Managing optional/required components Handling feature selections Automating inclusion, exclusion, or quantity logic Supporting configuration rules Ensuring sales reps configure solutions correctly Improving quote accuracy Providing guided selling experiences Because bundles fundamentally shape: Product catalog architecture Pricing structure Rules design Quote line generation Amendment/Renewal behavior Order + Billing outputs …they must be addressed early during discovery and scoping to avoid major redesign later. Salesforce implementation playbooks emphasize: Introduce all CPQ capabilities during discovery. Allow the customer to confirm whether a capability meets their use cases. Document decisions in the solution design before build. Therefore, bundles should always be a topic of discussion, but the customer chooses whether they need them based on business requirements. ❌ Why the other options are incorrect A. “Bundle configuration is necessary and should always be implemented. “Incorrect because: Not all customers need bundles. Some catalogs are simple, flat, or priced per unit with no component logic. Salesforce CPQ documentation does not state bundles are mandatory. C. “If they don’t use bundles now, they won’t need them later. “Incorrect because: Customers often evolve pricing and product strategies. Many legacy quoting tools do not support bundles, so current-state ≠ future-state. CPQ discovery must capture future-state needs. D. “Assume no bundle configuration unless customer brings it up. “Incorrect because: Customers often don’t know what CPQ bundles can do. CPQ consultants are responsible for educating customers on capabilities. Failing to introduce bundles leads to: Incorrect product catalog design Broken pricing logic Large rework later in the project This contradicts CPQ best-practice discovery methodology.