Free Copado Developer Certification Exam Copado-Developer Exam Practice Test

When deploying US1 and US2 in the same promotion, the old code in US2 is overwrittingthe most up-to-date code in US1. How can a developer resolve this issue?

• Resolve the conflict manually using the Online Conflict Resolution feature. (Might be this ans)
• Commit the code again in US1 before deploying.
• Use the Order User Stories by field in the Promotion record.
• Commit the code again in US2 before deploying.

While having work in progress in dev1, you are trying to deploy a small change to the Admin profile using the Copado CLI. After pushing and validating your changes, the validationdeployment is failing. why?

• The CLI push creates a deployment of the complete profile file which could include dependencies to work in progress.
• Copado has auto resolved the Git conflict in the profile with changes that are not available in the feature bcoranch.
• The resulting validation deployment will always include work in progress from the dev1 environment.
• Copado has auto resolved the Git conflict in the profile with changes that are not available in the source environment.

Which is TRUE about Static Code Analysis using CodeScan?

• You don't need to have a CodeScan account.
• CodeScan is only recommended to check Apex classes.
• You need to create Static Code Analysis Settings with CodeScan record type.
• All are correct.

After deleting a component in Dev1, Debbie has created a new user story to delete the component from the repository and upper environments. She has refreshed the metadata index before selecting the component. What can she do now in order to perform a destructive change commit of the component?

• Change the org credential and the environment on the user story and find the component in another org.
• Edit the metadata attachment on the user story and add the component.
• Click on Revert Metadata Index to return to the previous status.
• Use the Add Row button on the Commit Changes page and add the API name of the component.

When attempting to deploy a profile from a sandbox in the latest Salesforce Preview Instance toproduction in the latest Salesforce GA version, Debbie is receiving errors due to new userpermissions introduced in the Preview Instance that do not exist in the GA version of Salesforce.What can she do to move her changes forward?

• 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.

In Dev1, Debbie has added a new method to an Apex class. She has committed the user story anddeployed the user story to UAT. In Dev2, Dave has added a method to the same class and hasdeployed the changes to UAT. This has reported a conflict, so Dave has teamed up with Debbie andresolved it manually. What happens when the user stories are moved to the next environment?

• The conflict is reported again but just as a warning. They can deploy.
• There is no Git conflict since Copado has already stored the solution to the conflict.
• No conflict is reported. Copado uses the auto-resolve conflict resolution feature to apply the changes from the latest deployment to the Apex class.
• The conflict is reported again and they need to fix it manually in order to be able to deploy.

As part of your development process, developers can only create scratch orgs from Git packages. How can you ensure that developers can't select a different metadata source?

• 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.

Which is TRUE about Static Code Analysis using CodeScan?

• You don't need to have a CodeScan account.
• CodeScan is only recommended to check Apex classes.
• You need to create Static Code Analysis Settings with CodeScan record type.
• All are correct.

Dave would like to change the base branch on a user story from master to uat, but he can't see the Advanced button. As a Copado admin, what is the best way to fix this?

• Assigning Dave the Copado User managed permission set.
• Assigning Dave the System Admin profile.
• Assigning Dave the Edit User Story Commit Base Branch custom permission.
• Adding the Advanced button to the Commit Changes page layout.

The PMD rule Avoid SOQL queries inside loops should have the highest priority when running a static code analysis scan. How you can set this?

• Set the rule violation score in the PMD Default RuleSet to 1.
• Change the rule priority in the PMD Default RuleSet to 1. (I think this is correct as priority start from 1 still we need to check in PMD doc)
• Change the rule priority in the PMD Default RuleSet to 0.
• Create a new rule and set the priority to Blocker. Then, add it to the Default RuleSet.