Copado Copado-Developer Copado Developer Certification Exam Exam Practice Test

An error will be returned when committing.

If the component has never been committed successfully to Git, it won't be created in Git. If the component has already been tracked by Git, it won't be updated in Git.

If the component has never been committed successfully to Git, it won't be created in Git. If the component has already been tracked by Git, even if it is added to the .gitignore file, it will be updated in Git.

If the component has never been committed successfully to Git, it will be created in Git. If the component has already been tracked by Git, it won't be updated in Git.

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.

Merge the release branch into the destination branch.

Merge the feature branch into the source org's branch.

Merge the feature branch into the promotion branch.

B and C.

The committed component had no changes compared to the master branch.

Someone has deleted the commits directly in the feature branch.

The commit process failed.

Someone has used the Re-Create Feature Branch on the user story

True

False (I think this is correct, because in auto resolve copado merge it when there is conflict)

1

4

5

3

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

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

Changes Git operation selected. What could be the reason?

You have not been assigned the Edit User Story Commit Base Branch custom permission.

The Advanced button has not been added to the Commit Changes page layout.You have not been assigned the Edit User Story Commit Base Branch permission set.

The Base Branch field on the user story was left blank. (This is the correct ans)

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 but just as a warning. They are able to deploy.

Copado reports the conflict again and they need to fix it manually to be able to deploy.

Copado uses the conflict solution that was previously created.

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

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.