Option B is correct here. Automating corrective actions and regular tasks cuts down on manual effort, so ops teams can focus on more complex issues. C is more about reminders, which helps with coordination but doesn't really move the needle for operational efficiency like automation does. Pretty confident it's B but happy to see other takes.
Option B makes more sense to me since automating corrective actions covers more ground than just closing alerts. Regular operational task automation should directly boost efficiency, not just reduce alert fatigue. But I get why people pick A, cutting noise does help too. Pretty sure it's B but wouldn't be shocked if SAP wanted A in some contexts.
I don't think A or D are correct here. B, C, E show up consistently in SAP licensing info for Tricentis Test Automation term license, especially in current documentation. A is tempting since cloud stuff usually gets bundled, but it doesn't officially grant this license as per the latest docs I checked. Pretty sure that's right but if anyone's seen something newer, let me know.
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.
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.
Official guide and SAP Learning Hub both mention A for looking across several projects. Pretty sure that's what shows the multi-project dashboard, not just a single one's overview. Agree?
I don't think B (process mining) is part of SAP Cloud ALM for implementation. It's usually more relevant after go-live, not while setting up or planning tests and projects. A, C, and D match what you get for implementation features. Saw a similar question before and that's how it was split. Anyone else spot something I missed?
Pretty sure it's C here. Tags are flexible, users can define them any way needed in SAP Cloud ALM, while roles and risk levels are more fixed by the system. I saw similar phrasing in the official guide, so this matches up. Anybody see a different take?
I don’t think C belongs here. A, B, and E are what SAP Cloud ALM calls out for operations specifically-config monitoring (C) is more for administration/setup, not ongoing operations. Easy to confuse the scope though!