Summary:
The requirement is to prevent the sale of a single, globally available product in only two specific countries. The goal is to manage this restriction with minimal administrative effort and record creation. A disqualification rule is the most efficient tool for this scenario. It allows the product designer to create one rule for the new product that lists the two countries where it is not qualified to be sold. This is far simpler than creating a qualification rule that would need to list the 36 countries where it is allowed.

Correct Option:

C: Control availability with a disqualification rule.
This is the most efficient method. A single disqualification rule can be created for the new product.

The condition of the rule would specify that if the quote's or account's country is one of the two restricted nations, the product is disqualified and cannot be added to the quote.

This requires maintaining only one rule and one list of two countries, achieving the objective with a minimal number of records.

Incorrect Option:

A: Control availability with a recommendation rule.
A recommendation rule is used to suggest products to a user based on certain conditions. It does not restrict or prevent a product from being sold. It is a selling aid, not a governance tool.

B: Control availability with a qualification rule.
A qualification rule is used to define where a product is allowed to be sold. To use it for this scenario, the consultant would have to create a rule listing all 36 permitted countries. This is highly inefficient, difficult to maintain, and violates the requirement to create a minimal number of records compared to a simple disqualification rule.

Reference:
Salesforce Help: "Disqualify a Product" - This documentation explains that disqualification rules prevent products from being configured or added to a quote if the rule criteria are met, which is the precise functionality needed to block sales in two specific countries with a single, simple rule.

Summary:
In Salesforce Revenue Cloud, multicurrency support allows organizations to price products and manage transactions in multiple currencies. When multicurrency is enabled in an org with existing pricing procedures and decision tables, the Currency field may not automatically appear in the existing tables. To ensure that pricing logic accommodates multiple currencies, consultants must adjust the procedures and tables accordingly before reactivating them.

Correct Option:

B — Deactivate the pricing procedure and the associated decision table, then enable multicurrency and add the Currency field to the decision table before reactivating them
This is correct because existing decision tables cannot dynamically include new fields once activated. The proper steps are:

Deactivate the pricing procedure and its decision tables

Enable multicurrency in the Salesforce org

Add the Currency field to the decision tables

Reactivate the tables and procedures

This ensures that currency is recognized and used correctly in pricing calculations.

Incorrect Options:

A — Clone the pricing procedure and create a new decision table
This is unnecessary. Deactivation and field addition are sufficient; cloning adds complexity and can lead to versioning issues.

C — Enable multicurrency and wait for the Currency field to appear
This is incorrect because the Currency field does not automatically become available in active decision tables. Manual adjustment is required through deactivation.

Reference:
Salesforce Revenue Cloud Documentation → Multicurrency in Pricing Procedures, Decision Table Field Configuration, Activating/Deactivating Pricing Procedures.

Summary:
The requirement is to price a service (API calls) based on a specific, measurable attribute of the product—in this case, the number of API calls made. This is a classic use case for usage-based pricing. In Revenue Cloud, this is configured by creating a usage-based pricing model where the price is directly tied to a product attribute. The "Attribute Rate Entry" is the specific mechanism that defines the cost per unit (e.g., cost per API call) for a given attribute.

Correct Option:

B:Use attribute rate entries
This is the correct setup. Attribute rate entries are used to define a price per unit for a specific product attribute.

The consultant would create a usage-based product for "Cloud Storage," with an attribute called "Number of API Calls." An attribute rate entry would then be defined, for example, setting a price of $0.01 per API call. The system then calculates the total charge by multiplying the recorded usage (the attribute value) by this rate.

Incorrect Option:

A: Use base card entries
"Base card entries" is not a standard term or feature in Revenue Cloud for defining usage pricing. It does not correspond to a known configuration object or method for this scenario.

C: Use tier rate entries
Tier rate entries are used for tiered pricing, which is a different model. Tiered pricing applies different rates based on which usage range or tier a customer falls into (e.g., $0.10 per call for the first 1,000 calls, $0.08 per call for the next 2,000). While related to usage, it is not the most direct method if the requirement is a simple, flat rate per API call. Attribute rate entries are the foundation for this, and tiers can be added on top if needed.

Reference:
Salesforce Help: "Define Usage-Based Pricing" - This documentation explains how to set up products for usage-based pricing, which involves creating rate schedules and using attribute rate entries to define the price for a measurable attribute of the product.

Summary:
In Salesforce Revenue Cloud, proration ensures that customers are billed proportionally for partial subscription periods. When subscriptions start or end mid-period, a proration multiplier is applied to the standard price to calculate the charge for that partial period. Using the proration settings, such as aligning to the calendar and allowing partial periods, the system calculates the multiplier based on the number of days the subscription is active relative to the total days in the billing period.

Correct Option:

A — Proration Multiplier = Number of remaining days in March / Total number of days in March
This is correct because the subscription starts on March 20. The proration multiplier is based on the remaining days in March (March 20–31) relative to the total number of days in March (31 days). This ensures the customer is only billed for the portion of the month during which the subscription is active.

Incorrect Options:

B — Number of days used in March / Total number of days in March
This is incorrect because it calculates the multiplier based on days already passed rather than the remaining days for the billing period, which would undercharge the customer for the partial period.

C — Number of days used in a year / Total number of days in a year
This is incorrect because proration is calculated per billing period, not annually. Using annual days would misalign the charge for the partial month.

Reference:
Salesforce Revenue Cloud Documentation → Subscription Proration, Proration Multiplier Calculation, Align to Calendar Settings.

Summary:
The requirement is to stop a specific delinquent customer from being invoiced, not to stop the entire billing system or manually delete individual invoices. The standard, supported method for this in Revenue Cloud is to suspend billing for that customer's account. This action halts the generation of future invoices for the account while preserving the existing billing schedule data and history. This is an administrative function that requires the appropriate permissions.

Correct Option:

C: Assign themselves the Billing Administrator permission set, go to the customer’s account, and use the Suspend Billing button.
This is the correct and out-of-the-box method. The Suspend Billing action is a specific feature available on the Account object.

A user with the Billing Administrator permission set can access this button. When clicked, it prevents any future invoice runs from generating invoices for that specific account, effectively stopping the billing process for the delinquent customer as required.

Incorrect Option:

A: Assign themselves the Billing Administrator permission set, navigate to Scheduled Jobs, and delete the invoice scheduler’s scheduled jobs.
This is a drastic and incorrect action. Deleting the scheduled jobs for the invoice scheduler would stop billing for all customers, not just the delinquent one. This would severely disrupt business operations and is not a targeted solution.

B: Assign themselves the Billing Operations User permission set, go to the customer’s account, and delete their related pending invoices.
This is incorrect and addresses the symptom, not the cause. Deleting pending invoices is a manual, one-time action. It does not stop the system from generating new invoices for the customer in the next billing cycle. The Billing Operations User permission set also may not grant the ability to suspend billing.

Reference:
Salesforce Help: "Suspend and Resume Billing for an Account" - This official documentation describes the process of using the "Suspend Billing" button on an account record to stop all future billing for that specific customer, which is the exact capability needed to solve this scenario.