Which two should be taken to make sure the implementation is tested against the new release before it deploys to production?

A Revenue Cloud Consultant learns salesforce is deploying a new release during the course of the implementation.

Which two should be taken to make sure the implementation is tested against the new release before it deploys to production?
A . Review status.salesforce.com to determine refresh cutoff for the new release
B . The platform ensures that all sandboxes are upgraded at the same time so wait for the update.
C . Determine whether your sandbox is on a preview or non preview instance.
D . Submit a ticket to support when you want your sandbox Updated.

Answer: A,C

Explanation:

In Salesforce Revenue Cloud, when a new release is being deployed, it’s important to test the implementation against the new release before it deploys to production. This can be achieved by: Reviewing status.salesforce.com to determine refresh cutoff for the new release: Salesforce provides information about the refresh cutoff for the new release on status.salesforce.com. This allows you to know when the new release will be available in the sandbox for testing.

Determining whether your sandbox is on a preview or non-preview instance: Salesforce refreshes preview sandboxes a month before each major release. Regular, non-preview sandboxes are refreshed toward the end of the release cycle. Knowing whether your sandbox is on a preview or non-preview instance can help you plan your testing schedule accordingly.

It’s worth noting that while Salesforce ensures that all sandboxes are upgraded, the timing of the upgrade can vary depending on whether the sandbox is on a preview or non-preview instance.

Submitting a ticket to support when you want your sandbox updated is not a standard practice for preparing for a new release.

Reference

Test New Releases in a Sandbox Unit | Salesforce Trailhead Salesforce Introduces Revenue Cloud to Help Businesses Accelerate …