Free Copado Developer Certification Exam Copado-Developer Exam Practice Test

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.

How can you link the Copado CLI with the org where Copado is installed? Select all that apply!

• You can use the command sfdx plugins:install @copado/copado-cli.
• You can use the command sfdx copado:auth:set -a [myOrgAlias].
• You can use the command sfdx force:auth:web:login.
• You can use the command sfdx copado:auth:set -u [user@mycompany.com].

Debbie comitted some changes to the Opportunity Layout but, after deploying her changes from DEVto INT, she found her changes were not there due to an auto-resolved Git conflict she was not awareof. How can she prevent this from happening again in all future promotions?

• Manually promote and add Layout to the Exclude From Auto Resolve multi-select picklist field in the Promotion record.
• Remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.
• Manually promote and remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.
• Add Layout to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record

Even though Dave has defined NoTestRun in the Promotion Test Level field on his user story, thedeployment to production is running local tests. What could be the reason for this?

• NoTestRun can never be specified for a deployment to production.
• Deployments to production will always run the test level specified in the Promotion record.
• Deployments of Apex components to production will use RunLocalTest even though the test level on the user story is NoTestRun.
• Deployments of Apex components to production will always run the test level specified in the Promotion record

Debbie committed some changes to the Opportunity Layout but, after deploying her changes from DEV to INT, she found her changes were not there due to an auto-resolved Gitconflict she was not aware of. How can she prevent this from happening again in all future promotions?

• Add Layout to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record
• Manually promote and remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.
• Remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.
• Manually promote and add Layout to the Exclude From Auto Resolve multi-select picklist field in the Promotion rec

What happens when you use the Recommit Files Git operation and select the Re-Create Feature Branch checkbox? Select all that apply!You have reached the max number of allowed answers

• Both old and new Git commits are included in the feature branch.
• Previous commits are not included in the newlly created feature branch.
• The status of previous commit records is set to Commit not in branch.
• Previous commit records will be removed from the user story.

You have committed a custom field, but when you look at the feature branch, you don't see any updates. What do you need to check in order to troubleshoot the issue?

• Verify if the field is excluded in a YAML.
• Verify if the field is excluded in the metadata filter of the org credential.
• Verify if the field is excluded in an environment variable.
• Verify if the field is excluded in the .gitignore file.

Your company has had many issues with governor limits in the past, so you have beenrequested to give the highest relevance to the PMD rule Avoid making DML operations inApex Class. How can you do this?

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

You have work in progress in dev1. After retrieving from the org and pushing a hotfix for your Adminprofile from the Copado CLI, the validation deployment is failing. Why?

• The CLI push creates a deployment that includes the nested components in the profile file without including dependencies to work in progress.
• Copado has auto-resolved the Git conflict in the profile with changes that are not available in the feature branch.
• Copado has auto-resolved the Git conflict in the profile with changes that are not available in the source environment.
• While pushing your changes from the CLI, Copado deploys the complete profile file which could contain references to other work in progress in dev1.

You have created two different Account page layouts in Dev1, one for sales reps and and another onefor the support team. You have committed the two page layouts on a user story and you are ready todeploy them to the next environment. However, the sales manager makes a last-minute decision forhis team to continue using the standard Account page layout for now. What is the easiest way toprevent the sales reps layout from being deployed while deploying the support team layout?

• Delete the user story, create a new one and commit just the layout for the support team.
• Use the Recommit Files Git operation, flag the Create New Feature Branch checkbox and select only the layout for the support team.
• Use the Recommit Files Git operation, flag the Re-Create Feature Branch checkbox and select only the layout for the support team.
• Go to the user story and use the Destructive Changes Git operation to delete the sales reps layout. Then, use Commit Changes and just commit the layout for the support team.