Weekend Sale Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: xmas50

Copado Copado-Developer - Copado Developer Certification Exam

Page: 2 / 3
Total 84 questions

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?

A.

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

B.

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.

C.

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

D.

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

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?

A.

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

B.

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

C.

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

D.

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

What is the minimum Apex code coverage on a user story?

A.

The minimum test code coverage you specify on the environment.

B.

The minimum test code coverage you specify on the org credential.

C.

75%, which is the minimum code coverage required by Salesforce.

D.

85%, which is the minimum code coverage required by Salesforce.

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?

A.

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

B.

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

C.

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

D.

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

You want to give an existing PMD rule the lowest priority. How can you do this?

A.

Change the rule priority in the PMD Default RuleSet to Low Priority.

B.

Change the rule priority in the PMD Default RuleSet to 0.

C.

Change the rule priority in the PMD Default RuleSet to 5.

D.

Change the rule priority in the PMD Default RuleSet to Info.

Within the same sprint, Debbie added, a defaultPhone method and Dave added a defaultUrl method, both to the account operations class. Since, Debbie and Dave are working in their

individual sandboxes, after promoting the second user story, a Git conflict arose. They leamed up to solve the conflict using Copado's online conflict resolution feature. What

happens when both user stories are mass back-promoted?

A.

The defaultPhone method overwrites the other method.

B.

Copado uses semantic conflict resolution.

C.

The defaultUrl method overwrites the other method.

D.

Copado uses the conflict solution that was previously created.

How can you link the Copado CLI with the org where Copado is installed? Select all that apply!

A.

You can use the command sfdx plugins:install @copado/copado-cli.

B.

You can use the command sfdx copado:auth:set -a [myOrgAlias].

C.

You can use the command sfdx force:auth:web:login.

D.

You can use the command sfdx copado:auth:set -u [user@mycompany.com].

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.

Rob’s team wants to use data templates to import actual data into dev1 in order to test a

feature they have developed in that environment. What is the easiest way for them to ensure

no sensitive data is imported into dev1? Select all that apply!

A.

They will need to manually update the data included in sensitive fields one the deployment to dev1 is completed.

B.

They can create a Manual Task deployment step and manually remove the sensitive fields from dev1 once the deployment is completed.

C.

They can use the Replace Value option in the Object Fields tab of their data templates and enter a random value in the fields that contain sensitive data.

D.

They can use the Scramble Value option in the Object Fields tab of their data templates for fields that contain sensitive data, and Copado will replace the characters in the original value with random characters while deploying.

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.