Copado-Developer Exam Questions Instant Access

Question 1

Where can you control the available metadata sources when you create a scratch org from a user story?

AIn the Copado DX Mode picklist field in the Pipeline record.

BIn the Copado DX Mode picklist in the Environment record.

CIn the Copado DX Mode picklist field in the User Story record.

DIn the Copado DX Mode picklist field in the Dev Hub Org Credential record.

Answer : A

Question 2

Rob, would like to enforce the following quality gates when deploying to INT:

* A static code analysis for all Apex classes and triggers.

* A validation deployment for all Apex classes and triggers.

* A validation deployment for profiles.

What is the easiest way for him to address these requirements?

AHe needs to set up 1 connection behavior in INT with 2 quality gates, a Static Code Analysis for Apex classes and triggers and a validation for profiles and for Apex classes and triggers.

BHe needs to set up 1 connection behavior in DEV with 3 quality gates, one Static Code Analysis for Apex classes and triggers, one validation for Apex classes and triggers and one validation for profiles.

CHe needs to set up 3 connection behaviors in INT, one for the Static Code Analysis, one for the validation of Apex classes and triggers and one for the validation of profiles.

DHe needs to set up 2 connection behaviors in INT, one for the Static Code Analysis and one for the validation.

Answer : A

Question 3

Dave is getting an error message when trying to promote and deploy his Apex classes and

components to the integration environment. What could be the issue? Select all that apply!

AThe Apex code coverage is below the minimum Apex code coverage defined on the environment.

BApex tests were not executed on the user story

CThe minimum Apex code coverage defined on the user story is below the code coverage defined on the environment.

DThe Apex code coverage is below the minimum Apex code coverage defined in the Minimum Apex Code Coverage field on the user story.

Answer : A, D

Question 4

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?

AShe can go back to the user story where she committed the changes and use the Recommit Files Git operation.

BShe needs to create a new user story and commit again the permission set.

CShe needs to delete the user story, create a new one and commit again the field and the permission set.

DShe needs to create a new user story and commit again the custom field.

Answer : A

Question 5

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

When attempting to deploy a profile from a sandbox in the latest Salesforce Preview Instance to

production in the latest Salesforce GA version, Debbie is receiving errors due to new user

permissions introduced in the Preview Instance that do not exist in the GA version of Salesforce.

What can she do to move her changes forward?

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

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

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

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

Answer : B

Copado Developer Certification Copado-Developer Exam Questions