Create a YAML file to exclude the ManageSandboxes permission, add it to the pipeline and redeploy.

In the Git Promotion deployment step, use the Find and Replace feature to exclude the ManageSandboxes permission and redeploy.

Manually remove the ManageSandboxes permission from the destination branch and redeploy.

Update the .gitignore file in the uat branch to exclude the user permissions introduced in the higher API version and redeploy.

Select Git Packages in the Copado DX Mode picklist field in the User Story record.

Set the Copado DX Mode picklist field to Git Packages in all the environments.

Select Git Packages In the Copado DX Mode picklist field in the Pipeline record.

Remove from the developer profile the object level permissions to all metadata sources except for Git packages.

Update the .gitignore file in the master branch to exclude the user permissions introduced in the higher API version and redeploy.

Use the Find and Replace feature in the Git Promotion deployment step to exclude the user permissions introduced in the higher API version and redeploy.

Manually remove the ManageSandboxes permission from the destination branch and redeploy.

Log a case with Salesforce support to get the permissions enabled in production.

The user story will be displayed in the user stories behind count on the Pipeline page, and Dave will have to manually back-promote it by clicking on Back Promote & Deploy.

Copado will re-run the quality checks and automatically back-promote the user story to the other lower environments connected with UAT only if the relevant Apex tests pass. (This might be correct, still need to check)

Copado will send Dave a notification to let him know that the user story is ready to be backpromoted to other lower environments connected with UAT.

Copado will automatically back-promote the user story to other lower environments connected with UAT.

Set the rule priority in the PMD Default RuleSet to 5.

Set the rule violation score in the PMD Default RuleSet to 1.

Create a new rule and set the priority to Blocker. Then, add it to the Default RuleSet.

Change the rule priority in the PMD Default RuleSet to 1.

The base branch was set to master branch, and the component was not yet in production.

He did not have rights to delete the component in the source org.

The Re-Create Feature Branch checkbox was not flagged.

While adding a row, Dave misspelled the metadata API name of the component he wanted to delete in the metadata grid.

You can generate a default ruleset from Copado.

You need to have a CodeScan account.

CodeScan is only recommended to check Apex classes.

All are correct.

True

False (I think this is correct, because in auto resolve copado merge it when there is conflict)

In the project template

In the extensions.

In the user story.

In the scratch org definition.

Copado doesn ' t merge the feature branch with the environment source branch.

The Copado CLI push command doesn ' t trigger the merge of the feature branch with the environment branch.

The environment and org credential of the related user story were accidentally changed to a different one.

The Copado CLI push command doesn ' t trigger the merge of the feature branch with the promotion branch