Copado-Developer Exam Practice Test Instant Access

Question 1

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 validation

deployment is failing. why?

AThe CLI push creates a deployment of the complete profile file which could include dependencies to work in progress.

BCopado has auto resolved the Git conflict in the profile with changes that are not available in the feature bcoranch.

CThe resulting validation deployment will always include work in progress from the dev1 environment.

DCopado has auto resolved the Git conflict in the profile with changes that are not available in the source environment.

Answer : A

Question 2

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?

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

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

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

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

Answer : C

Question 3

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?

AManually promote and remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.

BManually promote and add ApexClass to the Exclude From Autore Solve multi-select picklist field in the Promotion record.

CRemove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.

DAdd ApexClass to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.

Answer : C

Question 4

The development team is complaining that when they try to select a metadata source in the scratch org wizard, they can only see Branches. Developers should be able to select any metadata source.

How you can fix this?

ASet the Copado DX Mode picklist field in the Pipeline record to 'None'.

BSet the Copado DX Mode picklist field in the Pipeline record to 'All Metadata Sources'.

CGive the developer profile the correct object level permissions to all metadata sources.

DSet the Copado DX Mode picklist field to 'Branches' in all the environments.

Answer : A

Question 5

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 Git

conflict she was not aware of. How can she prevent this from happening again in all future promotions?

AAdd Layout to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record

BManually promote and remove Layout from the Exclude From Auto Resolve multi-select
picklist field in the Promotion record.

CRemove Layout from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.

DManually promote and add Layout to the Exclude From Auto Resolve multi-select picklist field in the Promotion rec

Answer : A

Question 6

Dave has been assigned the task of deleting a custom object that has not been used in

production for a long time. After committing the destructive changes, he notices that no

feature branch has been created. What could be the reason?

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

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

CThe Re-Create Feature Branch checkbox was not flagged.

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

Answer : D

Question 7

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?

AVerify if the field is excluded in a YAML.

BVerify if the field is excluded in the metadata filter of the org credential.

CVerify if the field is excluded in an environment variable.

DVerify if the field is excluded in the .gitignore file.

Answer : A

Copado Developer Certification Copado-Developer Exam Practice Test