Dave has been asked to delete a custom object that has been deployed only to UAT. He has committed the object using the Destructive Changes Git operation. While reviewing the commits, he finds out that the commit has the status No changes.
What could be the reason for this?
- A . He doesn’t have permissions to use the Destructive Changes Git operation.
- B . He does not have CRED access to the object in the source org.
- C . The base branch was set to master branch.
- D . None are correct.
Dave would like to change the base branch on a user story from master to uat, but he can’t see the Advanced button.
As a Copado admin, what is the best way to fix this?
- A . Assigning Dave the Copado User managed permission set.
- B . Assigning Dave the System Admin profile.
- C . Assigning Dave the Edit User Story Commit Base Branch custom permission.
- D . Adding the Advanced button to the Commit Changes page layout.
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
You have a PMD static code analysis rule with priority 2. If this rule is violated once, what
will be the violation score?
- A . 3
- B . 4
- C . 6
- D . 2
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.
What is the command sfdx copado:auth:set -a [myOrgAlias] used for?
- A . It is used to link the Copado CLI with the org where Copado is installed.
- B . It is used to log in to the org where Copado is installed.
- C . It is used to authenticate the org credential of the org where Copado is installed.
- D . It is used to install the Copado CLI.
Rob would like to run Apex tests for all Apex metadata coming into the UAT environment and a compliance check for profiles and permission sets coming into the same environment.
How can he accomplish this?
- A . He needs to set up 3 connection behaviors in UAT with 1 quality gate each, 1 for Apex tests, 1 for the compliance check for permission sets and 1 for the compliance check for profiles.
- B . He needs to set up 1 connection behavior in UAT with 2 quality gates, an Apex test with Validation for the Apex elements and a Compliance Check both for profiles and for permission sets.
- C . He needs to set up 2 connection behaviors in UAT, one for the Apex tests and another one for the compliance check.
- D . He needs to set up 1 connection behavior in DEV with 2 quality gates, an Apex test with Validation for the Apex elements and a Compliance Check both for profiles and for permission sets.
In a sandbox, you have made some changes in the System Admin profile. When you try to deploy the profile, you are getting the error "Unknown User Permission: ManageSandboxes."
What can you do in
order to move your changes forward? Select all that apply!
- A . Create a YAML file to exclude the ManageSandboxes permission, add it to the pipeline and redeploy.
- B . In the Git Promotion deployment step, use the Find and Replace feature to exclude the ManageSandboxes permission and redeploy.
- C . Manually remove the ManageSandboxes permission from the destination branch and redeploy.
- D . Update the .gitignore file in the uat branch to exclude the user permissions introduced in the higher API version and redeploy.
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
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.
Debbie is deploying a user story with Apex components from UAT to production. The promotion test level on the user story is set to NoTestRun.
What test level is going to be enforced in the deployment to production?
- A . Run Specified Tests.
- B . No Test Run.
- C . Run Local Tests.
- D . Run All Tests In Org
You are using the auto-resolve conflict resolution feature, Copado will stop the merge of the feature branch into the promotion branch if it detects a conflict.
- A . True
- B . False (I think this is correct, because in auto resolve copado merge it when there is conflict)
After deleting the component in Dev1, Dave has accidentally refreshed the metadata index.
What can he do now in order to perform a destructive changes commit of the component? Select all that apply!
- A . He can recreate the component in Dev 1 and refresh the metadata index again.
- B . He can use the Org Credential lookup field in the Commit Changes page and find the component in another org.
- C . He can the Add Row button in the Commit Changes page and add the API name of the component.
- D . He can edit the metadata attachment on the user story and add the component.
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.
Dave has set up the following connection behavior in INT:
He has created a new profile in dev1 and is going to commit it on a user story.
What will happen after he clicks on Submit Changes?
- A . 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.
- B . 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.
- C . If the profile passes the compliance check, Copado will create a Promotion and a Deployment record and will automatically deploy it to INT.
- D . 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.
What happens when you use the Recommit Files Git operation and select the Re-Create Feature Branch checkbox? Select all that apply!
You have reached the max number of allowed answers
- A . Both old and new Git commits are included in the feature branch.
- B . Previous commits are not included in the newlly created feature branch.
- C . The status of previous commit records is set to Commit not in branch.
- D . Previous commit records will be removed from the user story.
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.
To which of the following components does Copado apply the resolution strategy "branch A wins over branch B"? Select all that apply!
- A . Apex classes
- B . Custom objects
- C . Profiles
- D . Layouts
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.
Which is TRUE about Static Code Analysis using CodeScan?
- A . You can generate a default ruleset from Copado.
- B . You need to have a CodeScan account.
- C . CodeScan is only recommended to check Apex classes.
- D . All are correct.
After pushing changes using the Copado CLI, you notice that the feature branch is being merged to a
different environment branch in your remote repository.
What could be the reason behind this?
- A . Copado doesn’t merge the feature branch with the environment source branch.
- B . The Copado CLI push command doesn’t trigger the merge of the feature branch with the environment branch.
- C . The environment and org credential of the related user story were accidentally changed to a different one.
- D . The Copado CLI push command doesn’t trigger the merge of the feature branch with the promotion branch
After deleting a component in Dev1, Debbie has created a new user story to delete the component from the repository and upper environments. She has refreshed the metadata index before selecting the component.
What can she do now in order to perform a destructive change commit of the component?
- A . Change the org credential and the environment on the user story and find the component in another org.
- B . Edit the metadata attachment on the user story and add the component.
- C . Click on Revert Metadata Index to return to the previous status.
- D . Use the Add Row button on the Commit Changes page and add the API name of the component.
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.
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.
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.
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.
As part of post scratch org creation, you would like to run a script to schedule a class in the scratch org.
How you can accomplish this?
- A . Create a deployment with an Apex step and add the script there. In the extensions in the scratch org wizard, select the deployment you have just created.
- B . In the extensions in the scratch org wizard, add the script that you want to execute.
- C . In the user story from where you are creating the scratch org, create an Apex deployment task and add the script there.
- D . A and C
What test level is applied to the deployment when you check the Promote & Deploy checkbox?
- A . The test level specified in the destination Org Credential record.
- B . The test level specified in the Promotion Test Level field on the User Story record.
- C . The test level specified in the Test Level field of the destination environment.
- D . The test level specified in the source environment.
The Staging Environment record has the Run all local tests checkbox enabled. A user story with Apex components and the promotion test level set to RunSpecifiedTests is being promoted and deployed.
What test level is going to be enforced?
- A . If the Run all local tests checkbox is enabled in the destination environment, every Copado deployment will always run all local tests.
- B . The promotion test level on the user story will win over the run all local tests specified in the environment.
- C . If the Run all local tests checkbox is enabled in the source environment, every Copado
deployment will always run all local tests. - D . Copado will run specified tests
Your company has had many issues with governor limits in the past, so you have been requested to give the highest relevance to the PMD rule Avoid making DML operations in Apex Class.
How can you do this?
- A . Set the rule priority in the PMD Default RuleSet to 5.
- B . Set the rule violation score in the PMD Default RuleSet to 1.
- C . Create a new rule and set the priority to Blocker. Then, add it to the Default RuleSet.
- D . Change the rule priority in the PMD Default RuleSet to 1.