매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Salesforce Certified Revenue Cloud Consultant 온라인 연습
최종 업데이트 시간: 2025년12월09일
당신은 온라인 연습 문제를 통해 Salesforce Rev-Con-201 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Rev-Con-201 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 90개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
In Salesforce Revenue Cloud, when product bundle behavior must change dynamically based on contextual data (e.g., Opportunity or Account fields), the correct approach is to use context-aware Constraint Models. Constraint Models can reference context attributes, such as the Industry field from the parent Opportunity, to dynamically control which product options are available or preselected during bundle configuration.
This approach ensures the configurator UI loads with the correct options and default selections without additional automation or UI components. The logic resides in the Constraint Model, which can define inclusion, exclusion, or recommendation rules that evaluate the context in real time.
Flows or configuration rules (like option B) don’t have direct access to Opportunity context within the configurator session; Constraint Models are specifically designed for contextual, attribute-driven logic.
Exact Extract from Salesforce CPQ Implementation Guide:
“Constraint Models can reference contextual data from related records such as Opportunity, Account, or Quote to drive dynamic product configuration behavior.”
Reference: Salesforce CPQ Implementation Guide ― Constraint Models and Context Awareness Salesforce Revenue Cloud Developer Guide ― Contextual Attributes in Product Configuration Salesforce CPQ Best Practices ― Dynamic Bundling Based on Context Data
정답:
Explanation:
In Salesforce Revenue Cloud, Product Attributes allow administrators to create dynamic, parameter-driven product definitions―removing the need for separate SKUs for every possible variation. Instead of defining millions of products (e.g., each skill as a unique product), organizations can create a single configurable product with attributes like skill type, level, region, or technology.
Attributes are defined through Product Attribute Sets and linked to one or more products, enabling sales reps to select attribute values during configuration or quoting. This approach drastically reduces catalog complexity, improves quote performance, and provides flexibility for price rules, approvals, and product logic.
By contrast, Product Categories and Product Classifications are for grouping, filtering, or reporting purposes, not for modeling variation.
Exact Extract from Salesforce CPQ Implementation Guide:
“Use Product Attributes to define product variations without creating multiple SKUs. Attributes allow a single product record to represent many configurations.”
Reference: Salesforce CPQ Implementation Guide ― Product Attributes and Attribute Sets
Salesforce Revenue Cloud Catalog Management Guide ― Reducing SKU Proliferation Using Attributes
Salesforce Revenue Cloud Solution Architect Handbook ― Dynamic Catalog Design for Large Enterprises
정답:
Explanation:
In Salesforce Revenue Cloud, assetization is the process of converting order products into active Asset records that track entitlements and subscriptions. When a business requires asset creation upon order activation (before submission for fulfillment), the proper approach is to use the Assetize Order flow.
The Assetize Order flow automatically generates assets for all qualifying order products as soon as
the order reaches the Activated status. It can be configured to run automatically through automation or invoked manually as part of an operational process.
The Submit Order for Fulfillment flow (option B) triggers fulfillment operations (e.g., provisioning or shipment) and is not intended for early asset creation. The Activate action alone does not create assets unless combined with the Assetize flow.
Exact Extract from Salesforce Subscription Management Implementation Guide:
“Use the Assetize Order flow to automatically create asset records when an order is activated. This process supports early asset creation prior to fulfillment.”
Reference: Salesforce Subscription Management Implementation Guide ― Assetize Order Flow Overview Salesforce Revenue Cloud Data Model ― Order to Asset Lifecycle Salesforce CPQ-Billing Integration Guide ― Automation for Asset Creation
정답:
Explanation:
In Salesforce Revenue Cloud, the Context Service provides reusable, versioned context definitions that define transactional data used in pricing, quoting, and billing operations. When a consultant wants to customize a standard context definition while retaining upgrade compatibility, the correct method is to extend the standard context (not clone it).
Extending a context (e.g., SalesTransactionContext) allows the new definition to inherit all standard nodes, attributes, and mappings from the base definition. The consultant can then safely add or override components without modifying the standard base. When Salesforce releases upgrades to the standard context, the extended context automatically inherits new or improved components, preserving all custom enhancements.
Cloning, on the other hand, creates a static copy and breaks the upgrade path―future improvements to the standard context would not be inherited.
Exact Extract from Salesforce Revenue Cloud Platform Guide:
“Extend a standard context to inherit its nodes and mappings. This ensures access to Salesforce-delivered updates while preserving your custom additions.”
Reference: Salesforce Revenue Cloud Platform Concepts ― Context Service and Context Definition Inheritance Salesforce CPQ & Billing Developer Guide ― Extending Standard Context Definitions
Salesforce Subscription Management Implementation Guide ― Best Practices for Context Extensibility
정답:
Explanation:
A Decision Table in Salesforce CPQ and Revenue Cloud Pricing is used to evaluate business rules and return outputs such as discounts, rates, or pricing logic. When deploying to a sandbox, both the Decision Table definition and any related custom objects that store rule inputs/outputs must first exist in the target environment.
The correct deployment sequence is:
Deploy the custom object and decision table metadata to the staging sandbox (ensuring structural consistency).
Map the decision table into the default pricing recipe, allowing it to integrate with the pricing engine for evaluations.
Refresh or sync Pricing, which updates the pricing engine and ensures all decision table logic and data are active and aligned with the current recipe configuration.
Importing data is optional if the data already exists in the source metadata; however, syncing pricing ensures that the engine recognizes the new logic.
Exact Extract from Salesforce Pricing and Decision Framework Guide:
“After deploying a Decision Table and its supporting custom objects, map it to the pricing recipe and refresh or sync pricing to activate the latest logic within the pricing engine.”
Reference: Salesforce Revenue Cloud Pricing Implementation Guide ― Decision Table Deployment Steps Salesforce CPQ Advanced Rules Framework ― Decision Table and Recipe Mapping
Salesforce Revenue Cloud Deployment Best Practices ― Pricing Engine Synchronization
정답:
Explanation:
Salesforce Revenue Cloud uses Context Definitions to pass contextual data―such as ContractId, AccountId, and OrderId―across transaction boundaries (e.g., from Order to Asset). To automatically capture and persist the Contract associated with an Asset, administrators should leverage Context Tags and Context Definitions instead of manual automation.
The correct solution is to:
Create a Contract lookup field on the Asset object.
Define a ContractId tag in the Asset context definition and map it to this lookup field.
Update the OrderToAsset Context Definition to map the Order’s ContractId tag to the Asset’s ContractId tag.
This ensures that when an Order creates Assets, the system automatically maps and populates the Contract reference based on context propagation, maintaining data consistency without extra automation.
Exact Extract from Salesforce Subscription Management Implementation Guide:
“Context Definitions allow for the propagation of key identifiers such as ContractId from Orders to downstream entities like Assets, ensuring accurate linkage for lifecycle management.”
Reference: Salesforce Subscription Management Implementation Guide ― Context Definitions and Tag Mapping Salesforce Revenue Cloud Data Model ― Order, Contract, and Asset Relationships Salesforce Billing and Asset Integration Guide ― OrderToAsset Context Configuration
정답:
Explanation:
In Salesforce CPQ, Constraint Models define validation, inclusion, and compatibility rules that control product configuration behavior. When a validation or warning depends on an attribute value of a single product, the logic should be defined at the Product Level Constraint Model.
In this scenario, the “Terabyte” attribute belongs to “Product A,” and the business rule requires displaying a warning message when the attribute exceeds 100. Implementing this at the Product Level Constraint Model ensures that the rule evaluates only that product’s context and triggers the message directly within the configuration page when users input the attribute value.
Quote-level constraint models are used for cross-product validations across multiple quote lines, not for product-specific attribute conditions. Therefore, option C correctly uses the Product Level Constraint Model.
Exact Extract from Salesforce CPQ Implementation Guide:
“Use Product Level Constraint Models when the validation logic applies to a specific product’s attributes or options. Use Quote Level models when the logic involves multiple products or quote lines.”
Reference: Salesforce CPQ Implementation Guide ― Constraint Models and Rule Hierarchies
Salesforce Revenue Cloud Developer Guide ― Product-Level Attribute Validation
Salesforce CPQ Best Practices ― Warning Messages and Validation Rules in Configuration
정답:
Explanation:
In Salesforce Revenue Cloud, a unified catalog strategy promotes scalability, governance, and efficient cross-sell and upsell opportunities across business units. For large B2B enterprises with diverse product models, the best approach is to lead discovery with a shared catalog architecture using reusable components, shared attributes, and modular selling models that can be adapted per business line.
This method ensures data consistency and allows governance teams to maintain a single source of truth for pricing, attributes, and approval logic―while still allowing flexibility for each line of business to define unique bundles or rules.
Creating separate catalogs (option C) or fully independent custom bundles (option B) leads to duplication, inconsistent logic, and high maintenance.
Exact Extract from Salesforce Revenue Cloud Catalog Management Guide:
“A unified catalog with shared components and attributes enables governance, reuse, and consistent cross-selling while still allowing flexibility for business-specific selling models.”
Reference: Salesforce Revenue Cloud Catalog Management Guide ― Unified Catalog Design Best Practices Salesforce CPQ Implementation Guide ― Modular Product Architecture and Shared Attributes Salesforce Revenue Cloud Solution Architect Handbook ― Catalog Governance and Scalability
정답:
Explanation:
Constraint Modeling Language (CML) defines logical relationships between quote line items, allowing administrators to automate dependency and compatibility logic in Salesforce CPQ.
The keyword require() explicitly establishes a dependency that ensures one product must exist when
another is present in a quote.
The correct syntax must define relationships with multiplicity ranges (e.g., [0..99]) and use the require() function, not constraint(), to specify the rule.
Option B meets these criteria:
type Quote {
relation desktop: Desktop[0..99];
relation monitor: Monitor[0..99];
require(desktop[Desktop], monitor[Monitor], "Desktop requires Monitor");
}
This ensures that when “Desktop” is added, “Monitor” is automatically included. The other options are incorrect because:
Option A uses the wrong function (constraint() instead of require()), which defines logical conditions but doesn’t enforce automatic inclusion.
Option C omits multiplicity, which is required for valid relationship definition.
Exact Extract from Salesforce CPQ Implementation Guide:
“The require() statement in CML defines a dependency rule so that when one product is selected, the dependent product is automatically added to the quote.”
Reference: Salesforce CPQ Implementation Guide ― Constraint Rules and CML Syntax Salesforce Revenue Cloud Developer Guide ― Defining Product Relationships in CML
정답:
Explanation:
In Salesforce Subscription Management and CPQ, Asset Actions and Asset State Periods track changes in asset quantity, pricing, and lifecycle states over time.
When the initial order for “Training” is activated, Salesforce creates:
One Asset Action for the creation (initial assetization).
One Asset State Period representing the active subscription for 50 seats.
When the same asset is amended later that day to add eight more seats (quantity change),
Salesforce generates:
A second Asset Action to record the amendment event (quantity increased by 8).
A second Asset State Period to represent the new asset state (58 seats active).
Each amendment creates a new Asset Action and corresponding State Period because Salesforce tracks historical lifecycle events for traceability, revenue recognition, and audit integrity.
The original state remains closed as of the amendment date, and a new one begins immediately.
Exact Extract from Salesforce Subscription Management Guide:
“Each amendment or change event generates a new Asset Action and corresponding Asset State
Period to represent the new effective asset configuration.”
Reference: Salesforce Subscription Management Implementation Guide ― Asset Actions and State Periods Salesforce CPQ-Billing Integration Guide ― Assetization Process Salesforce Revenue Cloud Data Model ― Asset Lifecycle Tracking
정답:
Explanation:
In Salesforce CPQ and Subscription Management, subscription cancellations cannot be backdated to a date earlier than the current date when the amendment or cancellation action is performed. This rule ensures data integrity between contracts, billing schedules, and revenue recognition.
In this case, the customer requested cancellation effective June 29, 2025, but the cancellation request was received on July 5, 2025. Salesforce enforces that the earliest possible effective date is the date the amendment or cancellation is executed―July 5, 2025―not any past date.
The only scenario where a contract can be canceled from the start date (June 20, 2025) is if the entire subscription term is voided before any billing or revenue recognition has occurred. Since the service was already active, that option isn’t valid.
Exact Extract from Salesforce Subscription Management Guide:
“Cancellations are effective on or after the date they are performed. Backdating cancellations before the current amendment date is not supported.”
Reference: Salesforce Subscription Management Implementation Guide ― Subscription Amendments and Cancellations
Salesforce CPQ Implementation Guide ― Amendment Rules and Effective Dates
Salesforce Revenue Cloud Contract Lifecycle Management ― Subscription Termination Behavior
정답:
Explanation:
In Salesforce Billing, a Credit Memo is used to record and manage customer credits resulting from negative transactions―such as cancellations, returns, or amendments that reduce invoiced amounts. When a negative amend or cancellation occurs, Salesforce Billing automatically generates Credit Memo Lines to represent the negative value associated with the customer’s account balance.
Credit Memos serve multiple purposes: they reflect negative invoice balances, adjust billing records, and can later be applied to open invoices to offset charges or prepare the account for payment settlement. This ensures financial accuracy while maintaining a clear audit trail for adjustments.
By contrast, Debit Memos represent additional charges to customers, while Cash Memos are related to direct cash entries and do not manage negative invoice balances.
Exact Extract from Salesforce Billing Implementation Guide:
“A Credit Memo is used to record and manage customer credits resulting from negative transactions such as cancellations, refunds, or adjustments. These credits can be applied to open invoices or retained for future settlements.”
Reference: Salesforce Billing Implementation Guide ― Credit and Debit Memo Management Salesforce Revenue Cloud Billing Data Model ― Credit Memo and Invoice Relationships Salesforce Billing Operations Guide ― Refunds and Credits Workflow
정답:
Explanation:
In Salesforce CPQ and Revenue Cloud, configurable bundle products are designed to give users flexibility during the quoting process. They contain multiple product options and optional features that can be customized based on customer needs. Each bundle can include predefined components (static) or user-selectable options (configurable), along with configurable attributes such as size, term, or license type.
This model allows sales representatives to create tailored product combinations by selecting or deselecting components, setting quantities, and adjusting attributes directly in the Quote Line Editor. This flexibility enhances accuracy in pricing and ensures the quote reflects the customer’s precise requirements.
By contrast, simple products are standalone and sold as-is, while static bundles have fixed options that cannot be altered during quoting. Therefore, option C correctly describes the behavior of configurable bundled products―allowing customization of both components and attributes at quote time.
Exact Extract from Salesforce CPQ Implementation Guide:
“Configurable bundles allow users to customize product components and define attributes at the time of quoting. This enables flexibility in configuring products to match customer requirements.”
Reference: Salesforce CPQ Implementation Guide ― Product Bundle Configuration and Attributes Salesforce Revenue Cloud Catalog Management ― Product Modeling Best Practices Salesforce CPQ Product Catalog Overview ― Simple, Static, and Configurable Bundles
정답:
Explanation:
The Context Service in Salesforce Revenue Cloud serves as a foundational service layer that centralizes and manages the data inputs, parameters, and contextual variables used in transactional processes across CPQ, Billing, and Subscription Management. Its core role is to ensure that every transaction―such as pricing, billing, revenue recognition, and tax calculation―operates with accurate, synchronized data context.
When a quote, order, or invoice is processed, the Context Service dynamically supplies key contextual data (like currency, account, tax jurisdiction, pricing date, and contractual terms) to ensure consistent calculations and business logic across different Revenue Cloud services. By doing so, it enables unified pricing and billing behavior and eliminates discrepancies that could occur from fragmented data sources.
Exact Extract from Salesforce Revenue Cloud Platform Concepts:
“Context Service provides the foundational context for transactional services in Revenue Cloud. It manages and distributes contextual data, such as customer, pricing, and tax parameters, enabling accurate calculations across CPQ, Billing, and Subscription Management.”
Reference: Salesforce Revenue Cloud Platform Concepts ― Context Service Overview
Salesforce CPQ and Billing Integration Guide ― Context Service Data Flow
Subscription Management Implementation Guide ― Transaction Context Handling
정답:
Explanation:
In Salesforce Billing, when an order product is activated, the system automatically creates a Billing Schedule Group (BSG) to manage all associated Billing Schedules (BSs). The BSG acts as the controlling record that connects multiple BSs generated for the same order product―whether from the initial order or from subsequent amendments.
When an amendment increases product quantity, Salesforce Billing does not create a new BSG; instead, it adds new BSs under the existing BSG. This design ensures that all billing activities for that product line―original or amended―are tracked within one consistent group.
Each Billing Schedule (BS) defines when and how much to bill, while the BSG provides a unified structure for reporting, synchronization, and downstream billing actions (e.g., invoicing, revenue recognition).
Thus, the persistence of the same BSG across amendments reflects correct and expected system behavior―ensuring billing continuity, preventing duplicate invoicing, and maintaining a single view of all schedules related to one order product.
Exact Extracts from Salesforce Revenue Cloud (Billing Implementation Guide):
“A Billing Schedule Group (BSG) acts as a container for all Billing Schedules associated with the same
order product. When amendments occur, Salesforce Billing generates new Billing Schedules under the existing Billing Schedule Group.”
“Billing Schedules define the timing and amounts to bill, while Billing Schedule Groups maintain continuity across amendments and changes.”
Reference (document/source names only; no URLs):
Salesforce Billing Implementation Guide ― Billing Schedules and Billing Schedule Groups Salesforce Billing Implementation Guide ― Amendments and Schedule Regeneration Salesforce Revenue Cloud Data Model ― Order Product to Billing Schedule Relationships