What can you do to prevent this?

Your company has multiple developers working in separate environments and sometimes your Apex

classes get overwritten.

What can you do to prevent this?
A . Activate Online Conflict Resolution feature by removing Apex classes from the Exclude From Auto Resolve field in the Promotion record.
B . Activate the Online Conflict Resolution feature by removing Apex classes from the Exclude From Auto Resolve field in the Pipeline record
C . Activate the Online Conflict Resolution feature by including Apex classes in the Exclude From Auto Resolve field in the Pipeline record
D . Create a validation rule to prevent the same Apex component from being committed in different environments.

Answer: B

How you can achieve this?

You would like to receive an alert whenever the static code analysis score of a user story is above 15.

How you can achieve this?
A . In the Environment record, set the Maximum SCA Score field to 15. Correct
B . In the Org Credential record, set the Maximum SCA Score field to 15.
C . In the Pipeline record, set the Maximum SCA Score to 15.
D . In the User Story record, set the Maximum SCA Score field to 15.

Answer: A

How can Debbie accomplish this?

While working in Dev1 Debbie has committed a new custom field “Amount” and a validation rule “Mandatory Amount” in the same user story. Later, during the sprint, the business analyst decided that the validation rule should not be included in this sprint but rather moved to the next sprint.

Nonetheless, the custom field must remain and be delivered in the current sprint.

How can Debbie accomplish this?
A . On the same user story, use the Destructive Changes Git operation to delete the validation rule.
B . Delete the user story, create a new one and commit only the custom field as retrieve only this time.
C . On the same user story, use the Recommit Files Git operation and deselect the validation rule.
D . On the same user story, use the Recommit Files Git operation, check the Re-Create Feature Branch checkbox, deselect the validation rule and recommit.

Answer: D

What test level is going to be enforced in the deployment to production?

Debbie is deploying a user story with Apex components from UAT to production. The promotion test level on the user story is set to RunSpecifiedTests.

What test level is going to be enforced in the deployment to production?
A . Deployments of Apex components to production will run at least specified tests.
B . Deployments of Apex components to production will always run specified tests.
C . When deploying Apex components, Copado will always run the test level specified in the Promotion Test Level field on the User Story record.
D . Deployments of Apex components to production will always run all tests.

Answer: D

How you can fix this?

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?
A . Set the Copado DX Mode picklist field in the Pipeline record to ‘None’.
B . Set the Copado DX Mode picklist field in the Pipeline record to ‘All Metadata Sources’.
C . Give the developer profile the correct object level permissions to all metadata sources.
D . Set the Copado DX Mode picklist field to ‘Branches’ in all the environments.

Answer: A

How can she prevent this from happening again in all future promotions?

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?
A . Add Layout to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record
B . Manually promote and remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.
C . Remove Layout from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.
D . Manually promote and add Layout to the Exclude From Auto Resolve multi-select picklist field in the Promotion rec

Answer: A

What could be the reason for this?

Even though Dave has defined NoTestRun in the Promotion Test Level field on his user story, the

deployment to production is running local tests.

What could be the reason for this?
A . NoTestRun can never be specified for a deployment to production.
B . Deployments to production will always run the test level specified in the Promotion record.
C . Deployments of Apex components to production will use RunLocalTest even though the test level on the user story is NoTestRun.
D . Deployments of Apex components to production will always run the test level specified in the Promotion record

Answer: C

deploying your templates to the next environment?

When working with data templates, how can you avoid getting validation rule errors when

deploying your templates to the next environment?
A . You can use a manual task to manually deactivate the validation rule before executing the deployment and reactivate it once the deployment is completed.
B . You can do a validation deployment to make sure you don’t have any offending records.
C . You can enable the Bypass Validation Rules checkbox in the data template.
D . All are correct.

Answer: D

story?

What happens with a component that is added to the .gitignore file and is later committed on a user

story?
A . An error will be returned when committing.
B . 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.
C . 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.
D . 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.

Answer: C