Q: 5
A project-specific deliverable is not part of the SAP Activate roadmap. How can you manage all tasks
that are related to that deliverable?
Options
Discussion
Option B, not A. The trap is thinking a custom team manages deliverables, but that's not how Activate structures tasks.
B . Custom deliverable is the SAP Activate way to manage work that's not in the standard roadmap. Release is more for go-live events, not tracking specific project tasks. I'm pretty sure but open if someone thinks otherwise.
Option B makes sense here because a custom deliverable lets you track all project-specific tasks in SAP Cloud ALM, exactly for situations like this. Creating a custom release (C) is more about deployment schedules than managing one-off deliverables. Pretty sure B is right, but open to discussion if anyone's seen it handled differently.
B
B
B works best here, since custom deliverable is exactly how SAP Cloud ALM lets you track new tasks outside the standard roadmap. Creating a custom team (A) is more about who owns it, not tracking tasks. Pretty sure it's B, but open to corrections.
Had something like this in a mock, it's B.
Seen this come up in official guides and practice exams. B is the way SAP Activate wants you to handle new, project-specific deliverables not already on the roadmap. Custom deliverable matches what the documentation says, pretty sure that's right.
B tbh. Custom deliverable is what SAP Activate expects for one-off project tasks not in the base roadmap. Releases are more for grouping go-lives, not tracking ad hoc work. Pretty sure about this, but let me know if I missed something.
C sounds about right to me. If you're handling a batch of tasks tied to a new project-specific deliverable, setting up a custom release could let you track everything together. Not totally sure though, as B looks tempting too if it's just about one-off stuff. Open to being wrong here.
Be respectful. No spam.
