Copado Certified Practice Exam

What mistake did Dave make that caused the user story to show no changes after committing the opportunity layout?

1. He did not mark the field as required

2. He marked the opportunity layout as Retrieve Only

3. He forgot to save his changes

4. He committed to the wrong branch

The correct answer is: He marked the opportunity layout as Retrieve Only

Marking the opportunity layout as Retrieve Only prevents any modifications from being committed. When a layout is set to this status, it means that the system treats it as read-only, and therefore, any changes made to the layout would not be captured during the commit process. This is critical in a deployment scenario where changes need to be tracked and reflected accurately. In contrast, other options might involve scenarios where changes could still be noted but would not reflect the fundamental issue of the layout's status impeding any modifications from being captured. For instance, not marking a field as required or forgetting to save changes may lead to missing updates, but they wouldn’t create a complete block on the visibility of changes like marking the layout as Retrieve Only. Committing to the wrong branch would result in changes appearing in an unexpected location, but again, not as starkly as the retrieve-only scenario. Thus, the condition of making a layout retrieve-only is directly responsible for causing the user story to show no changes after the commit.