Context Service provides a standardizedruntime data modelthrough which Revenue Management components access the data needed to execute transactional logic. Context definitions organize nodes, attributes, mappings, and tags representing transaction, account, product, pricing, and other business information.
This is especially important because Revenue Management calculations frequently require data distributed across multiple Salesforce objects. Rather than tightly coupling every pricing procedure, configuration rule, or downstream service directly to the physical object model, Context Service exposes relevant information through a reusable contextual representation. Hydration mappings load data into context, while Persistence mappings can write calculated or modified values back to source records.
Therefore, option B best describes its primary purpose: supplying and managing the inputs and variables required by transactional services and calculations.
Option A describes Contract Lifecycle Management and document-generation capabilities rather than Context Service. Option C describes Product Catalog Management, which manages products, classifications, attributes, bundles, categories, and selling models.
Context Service serves as foundational platform infrastructure connecting these functional domains to common contextual data.
Study Guide Reference:Agentforce Revenue Management Platform Concepts — Context Service Basics; context definitions; hydration, persistence, and transactional data.
===============
