Copado Certified Practice Exam

What action should you take to prevent a layout deletion user story from appearing in the User Stories Behind count?

1. Remove the user story from the history

2. Change the status of the user story

3. Flag the Exclude From CBM checkbox on the User Story record

4. Add an exception to the commit rules

The correct answer is: Flag the Exclude From CBM checkbox on the User Story record

To ensure that a layout deletion user story does not appear in the User Stories Behind count, flagging the "Exclude From CBM" checkbox on the User Story record is the most effective action. This checkbox is specifically designed to allow teams to manage which user stories should be counted in the CBM (Commitment Based Management) metrics. By using this option, you can maintain the integrity of your reporting while allowing for the necessary deletions or exclusions to occur without affecting overall project tracking and visibility. In the context of the other potential options, removing the user story from history is not a viable solution because it implies permanent deletion rather than proper management of the project data. Simply changing the status of the user story might not effectively remove it from the count, as it may not be recognized by the system as excluded from metrics. Adding an exception to the commit rules could complicate the process without directly addressing the need to exclude specific user stories from the count, potentially leading to unintended consequences in how other user stories are managed. Overall, the choice to utilize the Exclude From CBM checkbox offers a direct and controlled method to withhold specific user stories from being counted, which supports accurate project assessment and management.