Free Salesforce Rev-Con-201 Actual Exam Questions - Question 10 Discussion
provisioning after hardware delivery in its order-to-cash process. While configuring the Dynamic
Revenue Orchestrator (DRO) plan, the Fulfillment Designer notices the option for adding this delay is
not visible on the provisioning task.
What should the Revenue Cloud Consultant enable to add this option for the Fulfillment Designer?
Probably A; enabling Future-Dated Steps is the only setting that controls task delays.
Good points on A being needed for delays, but I’d add that the lack of the delay option usually isn’t about permissions (B) or linking (C)—those don’t control timing features. So yeah, A is the only logical choice here.
D imo, the key is definitely enabling Future-Dated Steps (A). Without that, the DRO plan won’t let you insert any time delays like the 2-day wait after hardware delivery.
It’s definitely not B or C since those don’t relate to scheduling delays—permissions or linking tasks won’t make the delay option appear. Future-Dated Steps (A) is the only setting that lets you add time gaps between tasks like this. Without it enabled, the system won’t show the delay option at all. So if the Fulfillment Designer can’t see it, the consultant needs to turn that feature on in DRO settings.
It’s A because enabling Future-Dated Steps is the only way to schedule delays between tasks in DRO. The other options don’t actually unlock the delay feature on provisioning tasks.
Guessing A as well. The delay is all about scheduling something to happen later, so you’d need that Future-Dated Steps feature turned on to see the option in the task. Permissions won’t add new functionality, and linking tasks doesn’t inherently create delays. Without enabling A, the system probably just won’t show any scheduling options for provisioning steps.
A imo. The 2-day delay basically means scheduling a task in the future, which is what the Future-Dated Steps feature is all about. Permissions (B) won’t add options that aren’t supported by the system, and linking tasks (C) doesn’t create delays, just connections. So enabling A should unlock that delay setting if the DRO version supports it.
The delay option showing up usually depends on whether the system supports scheduling future steps. So, enabling Future-Dated Steps (A) makes sense because it allows tasks to be deferred, which fits the 2-day delay requirement. Permissions like Modify All Data (B) wouldn't add new features, just more access, and linking tasks to step sources (C) sounds more about task organization than timing control. So, A seems like the right feature to enable here.
A imo