Practice Free AP-223 Exam Online Questions
Question #11
A Revenue Cloud user story for a Subscription-based Company Looking to replace their legacy system states “As a pricing Manager, bulk discounts will include previously purchased quantities for pricing calculations on the quote in order to reward loyal customers.
What should be included in the design of this solution?
- A . Custom Action to retrieve Purchased quantities from an external source
- B . Contracts, Subscriptions and Assets should be populated with historical data.
- C . Use a summary variable targeting the subscription object with a Price Rule.
- D . Legacy Orders and invoices should be migrated.
- E . Discount schedules with Cross Orders checked. (Choose 2 options)
Correct Answer: B,E
B,E
Explanation:
The requirement:
"Bulk discounts include previously purchased quantities for pricing calculations."
This refers to cross-order discounting, where historical quantities affect pricing on the new quote.
To support this:
✔ B C Contracts, Subscriptions and Assets should be populated with historical data CPQ reads existing Subscriptions/Assets to determine previously purchased quantities.
Historical install base must be migrated for correct discounting.
✔ E C Discount schedules with Cross Orders checked Salesforce CPQ includes an OOTB feature:
Discount Schedule → Cross Orders = TRUE This allows the quantity tiers to consider historical purchases.
Incorrect options:
A Custom Action unnecessary unless data is external (not indicated here).
C Summary variables cannot aggregate off-contract historical quantities.
D Migrating invoices is not required for quantity-based pricing.
Thus, the validated answers are B and E.
B,E
Explanation:
The requirement:
"Bulk discounts include previously purchased quantities for pricing calculations."
This refers to cross-order discounting, where historical quantities affect pricing on the new quote.
To support this:
✔ B C Contracts, Subscriptions and Assets should be populated with historical data CPQ reads existing Subscriptions/Assets to determine previously purchased quantities.
Historical install base must be migrated for correct discounting.
✔ E C Discount schedules with Cross Orders checked Salesforce CPQ includes an OOTB feature:
Discount Schedule → Cross Orders = TRUE This allows the quantity tiers to consider historical purchases.
Incorrect options:
A Custom Action unnecessary unless data is external (not indicated here).
C Summary variables cannot aggregate off-contract historical quantities.
D Migrating invoices is not required for quantity-based pricing.
Thus, the validated answers are B and E.
Question #12
Which feature is needed to split Order Products into different Invoice runs?
- A . Invoice Group
- B . Order by Quote Line Group
- C . Order by Group
- D . Invoice Batch
Correct Answer: A
A
Explanation:
The
question:
Which feature is needed to split Order Products into different Invoice Runs?
In Salesforce Billing, the feature that controls how order products are separated into different invoice
runs is Invoice Group.
✔ Why Invoice Group is the correct answer The Invoice Group field on: Order Product
Order Invoice is used to:
Separate order products into different invoices within the same invoice run, or Ensure specific order products are invoiced in different invoice runs entirely. The Billing Engine evaluates Invoice Group when generating invoices:
Order Products with different Invoice Group values → will be generated on different invoices or different invoice runs, depending on the configuration.
This is the official Salesforce Billing mechanism for splitting invoice generation.
A
Explanation:
The
question:
Which feature is needed to split Order Products into different Invoice Runs?
In Salesforce Billing, the feature that controls how order products are separated into different invoice
runs is Invoice Group.
✔ Why Invoice Group is the correct answer The Invoice Group field on: Order Product
Order Invoice is used to:
Separate order products into different invoices within the same invoice run, or Ensure specific order products are invoiced in different invoice runs entirely. The Billing Engine evaluates Invoice Group when generating invoices:
Order Products with different Invoice Group values → will be generated on different invoices or different invoice runs, depending on the configuration.
This is the official Salesforce Billing mechanism for splitting invoice generation.
Question #13
What are three reasons why you would need an AppExchange Solution to support generating a Document in support
of a Revenue Cloud Project?
- A . Contract Redlining
- B . Watermarks
- C . Invoice Generation
- D . Electronic Signature
- E . Attachments
Correct Answer: A,B,D
A,B,D
Explanation:
A Revenue Cloud project often requires enhanced document capabilities beyond native Salesforce CPQ or Billing.
✔ A ― Contract Redlining Requires document collaboration, versioning, and clause-level redline― not native in CPQ.
AppExchange apps like Conga, Nintex, DocuSign CLM support this.
✔ B ― Watermarks Not supported natively by CPQ Quote Templates or Billing invoice templates. Requires 3rd-party document generation.
✔ D ― Electronic Signature Salesforce does not provide native eSignature.
Common tools: DocuSign, Adobe Sign.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Invoice Generation
Salesforce Billing does generate invoices natively.
E ― Attachments
Salesforce Files/Attachments are natively supported; no AppExchange needed.
A,B,D
Explanation:
A Revenue Cloud project often requires enhanced document capabilities beyond native Salesforce CPQ or Billing.
✔ A ― Contract Redlining Requires document collaboration, versioning, and clause-level redline― not native in CPQ.
AppExchange apps like Conga, Nintex, DocuSign CLM support this.
✔ B ― Watermarks Not supported natively by CPQ Quote Templates or Billing invoice templates. Requires 3rd-party document generation.
✔ D ― Electronic Signature Salesforce does not provide native eSignature.
Common tools: DocuSign, Adobe Sign.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Invoice Generation
Salesforce Billing does generate invoices natively.
E ― Attachments
Salesforce Files/Attachments are natively supported; no AppExchange needed.
Question #13
What are three reasons why you would need an AppExchange Solution to support generating a Document in support
of a Revenue Cloud Project?
- A . Contract Redlining
- B . Watermarks
- C . Invoice Generation
- D . Electronic Signature
- E . Attachments
Correct Answer: A,B,D
A,B,D
Explanation:
A Revenue Cloud project often requires enhanced document capabilities beyond native Salesforce CPQ or Billing.
✔ A ― Contract Redlining Requires document collaboration, versioning, and clause-level redline― not native in CPQ.
AppExchange apps like Conga, Nintex, DocuSign CLM support this.
✔ B ― Watermarks Not supported natively by CPQ Quote Templates or Billing invoice templates. Requires 3rd-party document generation.
✔ D ― Electronic Signature Salesforce does not provide native eSignature.
Common tools: DocuSign, Adobe Sign.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Invoice Generation
Salesforce Billing does generate invoices natively.
E ― Attachments
Salesforce Files/Attachments are natively supported; no AppExchange needed.
A,B,D
Explanation:
A Revenue Cloud project often requires enhanced document capabilities beyond native Salesforce CPQ or Billing.
✔ A ― Contract Redlining Requires document collaboration, versioning, and clause-level redline― not native in CPQ.
AppExchange apps like Conga, Nintex, DocuSign CLM support this.
✔ B ― Watermarks Not supported natively by CPQ Quote Templates or Billing invoice templates. Requires 3rd-party document generation.
✔ D ― Electronic Signature Salesforce does not provide native eSignature.
Common tools: DocuSign, Adobe Sign.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Invoice Generation
Salesforce Billing does generate invoices natively.
E ― Attachments
Salesforce Files/Attachments are natively supported; no AppExchange needed.
Question #15
What are three reasons to establish a governance structure as part of your Revenue Cloud project?
Choose 3 answers
- A . To get agreement on the roles and responsibilities of the implementation team and customer
- B . To establish a communication plan between the implementation team, the customer and the work is coordinated between them
- C . To ensure the implementation team can work independently for most of the project with little to no input from the customer
- D . To ensure the implementation team is aligned with the customer on assigned work
- E . To assign more work for the customer when it comes to designing and building the Revenue Cloud solution
Correct Answer: A,B,D
A,B,D
Explanation:
A solid governance structure is a required component of every Salesforce Revenue Cloud implementation (CPQ + Billing). Salesforce’s project methodology stresses governance for:
Clear roles and responsibilities
Alignment across business and technical teams
Controlled communication flows
Coordinated delivery
Risk and issue management
Change control
Let’s evaluate each option:
✅ A. To get agreement on the roles and responsibilities of the implementation team and customer This is one of the core purposes of governance.
The RACI structure (Responsible, Accountable, Consulted, Informed) is part of governance setup and ensures:
No duplication of work
No gaps in ownership
Clear escalation paths
✔ This is correct.
❌ C. To ensure the implementation team can work independently with little customer input This is the opposite of governance.
Revenue Cloud projects require constant alignment with the customer across:
Catalog structure
Pricing rules
Billing cycles
Renewals
Integration design
Customer involvement is essential.
✖ Not a valid reason.
❌ E. To assign more work to the customer Governance is not a method to increase customer workload.
It ensures collaboration, not burden shifting.
✖ Incorrect.
✅ B. To establish a communication plan between teams and coordinate the work Governance defines how:
PMs communicate
Status reports occur
Risks/issues are escalated
Decisions are documented
This is a fundamental governance objective.
✔ Correct.
✅ D. To ensure the implementation team is aligned with the customer on assigned work Exactly. Governance guarantees alignment on:
Scope Requirements Sprint commitments Priorities
Change requests
✔ Correct.
✔ Final Verified Answer A, B, D
A,B,D
Explanation:
A solid governance structure is a required component of every Salesforce Revenue Cloud implementation (CPQ + Billing). Salesforce’s project methodology stresses governance for:
Clear roles and responsibilities
Alignment across business and technical teams
Controlled communication flows
Coordinated delivery
Risk and issue management
Change control
Let’s evaluate each option:
✅ A. To get agreement on the roles and responsibilities of the implementation team and customer This is one of the core purposes of governance.
The RACI structure (Responsible, Accountable, Consulted, Informed) is part of governance setup and ensures:
No duplication of work
No gaps in ownership
Clear escalation paths
✔ This is correct.
❌ C. To ensure the implementation team can work independently with little customer input This is the opposite of governance.
Revenue Cloud projects require constant alignment with the customer across:
Catalog structure
Pricing rules
Billing cycles
Renewals
Integration design
Customer involvement is essential.
✖ Not a valid reason.
❌ E. To assign more work to the customer Governance is not a method to increase customer workload.
It ensures collaboration, not burden shifting.
✖ Incorrect.
✅ B. To establish a communication plan between teams and coordinate the work Governance defines how:
PMs communicate
Status reports occur
Risks/issues are escalated
Decisions are documented
This is a fundamental governance objective.
✔ Correct.
✅ D. To ensure the implementation team is aligned with the customer on assigned work Exactly. Governance guarantees alignment on:
Scope Requirements Sprint commitments Priorities
Change requests
✔ Correct.
✔ Final Verified Answer A, B, D
Question #16
Our customer is headquartered in the US but has operations in Germany. The German operation has CPQ installed in their own EU instance of Salesforce.
Which Service Region should be defined for the European instance of CPQ in order to optimize calculation performance?
- A . Service Region has no performance impact
- B . North America
- C . Japan
- D . Europe
- E . Australia
Correct Answer: D
D
Explanation:
The CPQ Quote Calculator runs in a designated Service Region. Performance increases significantly
when:
The service region is geographically close to the Salesforce org.
Since the org is hosted in the EU:
✔ D ― Europe is the correct service region, which reduces latency and speeds calculation.
Why the others are wrong: Option
Why Incorrect
A ― No performance impact
100% incorrect; region affects latency heavily.
B ― North America
Far from EU, adds latency.
C ― Japan
Even slower.
E ― Australia
Worst possible latency option.
Thus D is correct.
D
Explanation:
The CPQ Quote Calculator runs in a designated Service Region. Performance increases significantly
when:
The service region is geographically close to the Salesforce org.
Since the org is hosted in the EU:
✔ D ― Europe is the correct service region, which reduces latency and speeds calculation.
Why the others are wrong: Option
Why Incorrect
A ― No performance impact
100% incorrect; region affects latency heavily.
B ― North America
Far from EU, adds latency.
C ― Japan
Even slower.
E ― Australia
Worst possible latency option.
Thus D is correct.
Question #17
What does RASIC stand for?
- A . Responsible, Actionable, Supporting, Informed, Consulted
- B . Responsible, Actionable, Supporting, Informed, Communicate
- C . React, Action, Support, Informed, Consulted
- D . Responsible, Accountable, Supporting, Informed, Consulted
Correct Answer: D
D
Explanation:
RASIC is a well-known responsibility matrix used in Salesforce projects.
✔ Correct definition: R ― Responsible A ― Accountable
S ― Supporting I ― Informed
C ― Consulted
D
Explanation:
RASIC is a well-known responsibility matrix used in Salesforce projects.
✔ Correct definition: R ― Responsible A ― Accountable
S ― Supporting I ― Informed
C ― Consulted
Question #18
What does the ‘safe harbor’ slide at the beginning of every salesforce presentation means?
- A . roadmap capability will be released exactly as they are demonstrated
- B . new release capabilities will not have impact to existing implementations
- C . anything presented from salesforce must be kept confidential
- D . mergers and acquisitions integrations are immediate
- E . You and or your customer are making scoping, design, planning, purchasing making decisions based on current and available capabilities.
Correct Answer: E
E
Explanation:
The Salesforce Safe Harbor statement exists to remind customers:
They should only make scoping, planning, design, and purchasing decisions based on current, available functionality, not forward-looking statements or roadmap presentations.
Salesforce does not guarantee:
Release timing
Exact feature delivery
Backward compatibility
E
Explanation:
The Salesforce Safe Harbor statement exists to remind customers:
They should only make scoping, planning, design, and purchasing decisions based on current, available functionality, not forward-looking statements or roadmap presentations.
Salesforce does not guarantee:
Release timing
Exact feature delivery
Backward compatibility
Question #19
What are three key characteristics of an implementation partner leading are venue cloud scoping session?
- A . Excellent Communication Skills both verbal and written
- B . Being effective at planning, monitoring and reviewing
- C . Having deep knowledge of competitor Products
- D . Experience in a selling role with quota responsibilities
- E . Understanding design pitfalls and Mitigation actions to course correct.
Correct Answer: A,B,E
A,B,E
Explanation:
A partner leading a Revenue Cloud Scoping session requires:
✔ A ― Strong communication skills Essential for facilitating workshops, documenting requirements, and aligning stakeholders.
✔ B ― Effective at planning, monitoring, reviewing Scoping is structured, requires:
Agenda control
Risk identification
Note capture
Validation cycles
✔ E ― Understanding design pitfalls & mitigation Critical in CPQ + Billing, where poor scoping leads
to:
Wrong pricing model
Incorrect renewal logic
Billing edge cases
Data migration problems
A good partner surfaces these risks early.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Knowledge of competitor products
Not relevant to scoping Salesforce Revenue Cloud.
D ― Experience with quota-carrying sales roles
Helpful but not foundational to scoping complex CPQ + Billing architecture.
Final answer for Q49 = A, B, E
A,B,E
Explanation:
A partner leading a Revenue Cloud Scoping session requires:
✔ A ― Strong communication skills Essential for facilitating workshops, documenting requirements, and aligning stakeholders.
✔ B ― Effective at planning, monitoring, reviewing Scoping is structured, requires:
Agenda control
Risk identification
Note capture
Validation cycles
✔ E ― Understanding design pitfalls & mitigation Critical in CPQ + Billing, where poor scoping leads
to:
Wrong pricing model
Incorrect renewal logic
Billing edge cases
Data migration problems
A good partner surfaces these risks early.
Why the wrong answers are incorrect: Option
Why Incorrect
C ― Knowledge of competitor products
Not relevant to scoping Salesforce Revenue Cloud.
D ― Experience with quota-carrying sales roles
Helpful but not foundational to scoping complex CPQ + Billing architecture.
Final answer for Q49 = A, B, E
Question #20
Universal Containers is implementing Revenue Cloud for a business unit that already uses a legacy CPQ system, what consideration should be taken as the implementation partner?
- A . Map legacy CPQ system capabilities to ensure there is no loss of logic from the older system
- B . Customize Revenue Clouds user interface so the customer experiences no major interruption to the new system
- C . Transform the customer’s business processes, capture new requirements for the new Revenue Cloud technology
- D . Keep the legacy CPQ system and build to the gaps in Revenue Cloud so the customer can use both systems to satisfy requirements
Correct Answer: C
C
Explanation:
Revenue Cloud implementations should NOT replicate outdated legacy CPQ logic.
Instead, Salesforce best practices require business transformation:
Understand current and future-state processes
Challenge legacy limitations
Use standard functionality wherever possible
Remove unnecessary customizations
✔ Correct Answer C Options A, B, and D represent anti-patterns:
Option
Why Incorrect
A ― Map legacy CPQ logic
Leads to replicating outdated processes rather than improvement.
B ― Customize UI to mimic legacy
Increases technical debt and destroys scalability.
D ― Keep legacy CPQ
Two CPQ systems create conflicts and are not recommended.
Thus C is correct.
C
Explanation:
Revenue Cloud implementations should NOT replicate outdated legacy CPQ logic.
Instead, Salesforce best practices require business transformation:
Understand current and future-state processes
Challenge legacy limitations
Use standard functionality wherever possible
Remove unnecessary customizations
✔ Correct Answer C Options A, B, and D represent anti-patterns:
Option
Why Incorrect
A ― Map legacy CPQ logic
Leads to replicating outdated processes rather than improvement.
B ― Customize UI to mimic legacy
Increases technical debt and destroys scalability.
D ― Keep legacy CPQ
Two CPQ systems create conflicts and are not recommended.
Thus C is correct.