Which valid actions can a consultant perform on a standard context definition?

Standard context definitions are Salesforce-managed artifacts and therefore should not be directly edited like ordinary customer-created metadata. The supported customization approaches identified by the source areExtendandClone.

Extending is appropriate when the consultant wants to inherit the standard definition—including its nodes, attributes, and mappings—and add customer-specific components while retaining a relationship with the Salesforce-managed base definition. This is typically the preferred option when upgrade compatibility is important.

Cloning creates an independent definition based on the standard definition at a point in time. It provides greater separation but does not provide the same inheritance relationship as extension.

Option A implies direct editing after a simple copy operation and is not the supported pair of standard-context actions identified in Revenue Management. Option C is invalid because consultants do not deactivate and directly modify Salesforce-managed standard definitions as their customization strategy.

The governing principle is toextend or clone standard metadata rather than modifying the managed source definition.

Study Guide Reference:Agentforce Revenue Management Platform Concepts — Context Service; standard context definitions; Extend versus Clone.

===============