A customer currently uses the standard Quote and Order objects and wants to distinguish the...

Revenue Management deliberately reuses standard Salesforce transaction objects such as Quote and Order. Therefore, the object type itself does not reliably identify whether a particular record participates in Revenue Lifecycle Management. The supplied source identifiesApplication Usage Assignmentas the out-of-the-box mechanism for making that distinction.

A related Application Usage Assignment record with the Revenue Lifecycle Management value indicates that the transaction record belongs to the Revenue Management application context. This provides a platform-level classification without forcing organizations to introduce custom fields or depend on arbitrary Record Types.

Option B is incorrect because Revenue Management does not require every Quote and Order record to use a special Revenue Lifecycle Management Record Type as the definitive identifier. Option C likewise treats Transaction Type as an application-origin marker, when transaction type primarily describes transactional behavior rather than proving which application framework created or owns the record.

The design principle is to use Salesforce ' s application-assignment metadata rather than implementing redundant custom categorization.

Study Guide Reference:Agentforce Revenue Management Platform Concepts — Revenue Management data model; Application Usage Assignment; standard Quote and Order integration.

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