Copado-Developer Sample Questions Answers

The minimum Apex code coverage of the user story cannot be below the minimum Apex code coverage of the environment.

The minimum Apex code coverage of the user story cannot be above the minimum Apex code coverage of the environment.

The minimum Apex code coverage of the user story cannot be different from the minimum Apex code coverage of the environment.

The minimum Apex code coverage on the user story cannot be modified.

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

Resolve the conflict manually using the Online Conflict Resolution feature. (Might be this ans)

Commit the code again in US1 before deploying.

Use the Order User Stories by field in the Promotion record.

Commit the code again in US2 before deploying.

Custom object translations

Apex triggers

Apex classes

Profiles

2, one for Apex classes and triggers and one for profiles and permission sets. (This is correct ans)

3, one for profiles and permission sets, one for Apex classes and one for Apex triggers.

4, one for each metadata type.

3, one for the Apex components (classes and triggers), one for profiles and one for permission sets.

required field: '___REPLACEVALUE___'.

required field: '(?s)(\n\s*(?:(?!).)*?___REPLACEVALUE___(?:(?!

ields>).)*?)'.

required field: '(?s)(\n\s*)'.

required field:

'(?s)(\n\s*(?:(?!).)*?___REPLACEVALUE___(?:(?!).)*?)'.

4

3

2

1

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

Apex tests were not executed on the user story

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

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

If the Run all local tests checkbox is enabled in the destination environment, every Copado deployment will always run all local tests.

The promotion test level on the user story will win over the run all local tests specified in the environment.

If the Run all local tests checkbox is enabled in the source environment, every Copado deployment will always run all local tests.

Copado will run specified tests

3

4

6

2

Apex classes

Custom objects

Profiles

Layouts

If the profile passes the compliance check, the user story will be displayed in the count of user stories ahead on the Pipeline page and Dave will have to manually promote it from there by clicking on Promote & Deploy.

If the profile passes the compliance check, Copado will create a Promotion and a Deployment record and Dave will need to click on Deploy from the Deployment record.

If the profile passes the compliance check, Copado will create a Promotion and a Deployment record and will automatically deploy it to INT.

If the profile passes the compliance check, Copado will create a Promotion and a Deployment record and Dave will need to click on Promote & Deploy from the Deployment

record.

Rob will need to deactivate the validation rules in production and set the Manual Task deployment

step to Complete. After this, he will receive an email informing him the task has been completed and

the deployment of the data template will be triggered.

Rob will need to deactivate the validation rules in production. Once this is done, the data template will be deployed. Lastly, he will need to set the manual task to Complete.

The data template will be migrated and, once this is done, Rob will receive an email notification for the manual task to be completed. He will then deactivate the validation rules in production and set the manual task to Complete.

Rob will receive an email notification for the manual task to deactivate the validation rules in production. Once he deactivates the validation rules, he will need to set the Manual Task deployment step to Complete. Next, the template will be deployed.

The conflict is reported again but just as a warning. They can deploy.

There is no Git conflict since Copado has already stored the solution to the conflict.

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 and they need to fix it manually in order to be able to deploy.

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.

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

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

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

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

packagePrefix__.*?.

packagePrefix__fieldName1, packagePrefix__fieldName2,

packagePrefix__fieldName3 and so on.

{!Environment.classes/packagePrefix__.*}.

This is not possible.

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.

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)

Profiles

Custom objects

Apex triggers

Visualforce pages

Commit the code again before deploying.

Resolve the conflict manually using the Online Conflict Resolution.

Change the user story base branch to 'Dev'

All are correct.

The user who created the data templates used Scramble with Format in some of the fields to avoid moving sensitive data.

Dave has imported the wrong data template.

The user who created the data templates used Scramble Value in some of the fields to leave out sensitive data.

They used the Global Find and Replace feature to scramble the values