Salesforce ' sSafe Harborprinciple means customers and implementation teams must make purchasing, architectural, and deployment decisions based on functionality that is currentlygenerally available, rather than functionality discussed as future direction.
Roadmap information can be useful for strategic awareness, but future features can be delayed, modified substantially, renamed, or never delivered. A production solution therefore must not have a critical dependency on an unreleased roadmap capability.
Option A incorrectly assumes that roadmap announcements guarantee availability. They do not. Option C is also inappropriate because an informal or verbal confirmation from a Product Manager does not change the Safe Harbor principle or convert an unreleased capability into generally available functionality.
The correct implementation approach is to design against capabilities that exist and are supported at the time of the project. If future functionality later becomes generally available, the organization can evaluate whether adopting it produces sufficient benefit to justify architectural changes.
This is particularly important for Revenue Management projects because product roadmaps can span catalog, pricing, contracts, billing, orchestration, assets, and Agentforce capabilities.
Study Guide Reference:Implementation Readiness — Salesforce Safe Harbor; solution design governance; generally available functionality.
