Dave comitted a new method on the AccountOperations class but, after deploying his changes from DEV to INT, he found his changes were not there due to an auto-resolved Git conflict he was not aware of. What could he have done to prevent this from happening just in this particular promotion?

• A.Manually promote and add ApexClass to the Exclude From Autore Solve multi-select picklist field in the Promotion record.
• B.Remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.
• C.Add ApexClass to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.
• D.Manually promote and remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.

Comment: *

Name: *

Email: *

Verification: *

For which of the following components is it not recommended to use auto-resolve? Select all that apply!
You have reached the max number of allowed answers

• A.Custom objects
• B.Visualforce pages
• C.Apex triggers
• D.Profiles

Comment: *

Name: *

Email: *

Verification: *

Debbie is deploying a user story with Apex components from UAT to production. The promotion test level on the user story is set to NoTestRun. What test level is going to be enforced in the deployment to production?

• A.Run Specified Tests.
• B.Run All Tests In Org
• C.Run Local Tests.
• D.No Test Run.

Comment: *

Name: *

Email: *

Verification: *

After pushing changes using the Copado CLI, you notice that the feature branch is being merged to a different environment branch in your remote repository. What could be the reason behind this?

• A.The environment and org credential of the related user story were accidentally changed to a different one.(Not Sure)
• B.The Copado CLI push command doesn't trigger the merge of the feature branch with the environment branch.
• C.Copado doesn't merge the feature branch with the environment source branch.
• D.The Copado CLI push command doesn't trigger the merge of the feature branch with the promotion branch.

Comment: *

Name: *

Email: *

Verification: *

Debbie has created a new custom field in Dev1. She commits it on a user story together with the permission set to deploy FLS. After committing the changes, she realizes she forgot to grant the permission set access to the field in Dev1, so she goes back to Dev1 and updates the FLS. What is the easiest way to ensure the FLS is deployed to the next environment together with the field?

• A.She can go back to the user story where she committed the changes and use the Recommit Files Git operation.
• B.She needs to create a new user story and commit again the permission set.
• C.She needs to create a new user story and commit again the custom field.
• D.She needs to delete the user story, create a new one and commit again the field and the permission set.

Comment: *

Name: *

Email: *

Verification: *