Copado Developer - Practice Questions With Solutions

Copado Developer - Practice Questions With Solutions (From Practice Test And Copado Academy Quizzes) 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? Right Ans - Add Layout to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record Dave committed a new method on the AccountOperations class but, after deploying his changes from DEV to INT, he found his changes were not there due to an auto-resolved Git conflict he was not aware of. What could he have done to prevent this from happening just in this particular promotion?** Right Ans - Remove ApexClass from the Exclude From Auto Resolve multi- select picklist field in the Pipeline record.Manually promote and remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.Who can see the Advanced button in button on the Commit Changes page?Right Ans - Any user with Edit User Story Commit Base Branch custom permission assigned You're unable to see the Advanced button on the Commit Changes page with the Destructive Changes Git operation selected. What could be the reason?Right Ans - You have not been assigned the Edit User Story Commit Base Branch custom permission.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? Right Ans - Assigning Dave the Edit User Story Commit Base Branch custom permission.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?Right Ans - Run Local Tests. 1 / 3

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? Right Ans - If the Run all local tests checkbox is enabled in the destination environment, every Copado deployment will always run all local 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 RunSpecifiedTests. What test level is going to be enforced in the deployment to production? Right Ans - Deployments of Apex components to production will always run all tests.After passing Apex tests on a user story and deploying an Apex hotfix user story from dev to uat, other tests are failing in the validation deployment in production. How is this possible if the deployment didn't fail before? (2) Right Ans - (1) The promotion test level on the user story was set to RunSpecifiedTests but the Run All Tests checkbox is enabled in the Production Environment record.(2) The promotion test level on the user story was set to NoTestRun.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? Right Ans - Deployments of Apex components to production will use RunLocalTest even though the test level on the user story is NoTestRun.What test level is applied to the deployment when you check the Promote & Deploy checkbox? Right Ans - The test level specified in the Promotion Test Level field on the User Story record.Which IS TRUE about Static Code Analysis using Code Scan? (3) Right Ans - (1) You can review the violations from the Static Code Analysis Result related list on the User Story record.(2) You need to have a CodeScan account. 2 / 3

(3) You need to create Static Code Analysis Settings with CodeScan record type.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? Right Ans - The environment and org credential of the related user story were accidentally changed to a different one.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? Right Ans - The CLI push creates a deployment of the complete profile file which could include dependencies to work in progress.Which of the following expressions is a correct regex expression that finds the value in the required tag of a field? Right Ans - required '(?s)(\n\ s*(?:(?!).)*?___REPLACEVALUE___(?:(?!).)*?)'.Dave is getting an error message when trying to promote and deploy his Apex classes and components to the integration environment. What could be the issue? (2) Right Ans - (1) The Apex code coverage is below the minimum Apex code coverage defined on the environment.(2) The Apex code coverage is below the minimum Apex code coverage defined in the Minimum Apex Code Coverage field on the user story.You want to give an existing PMD rule the lowest priority. How can you do this? Right Ans - Change the rule priority in the PMD Default RuleSet to 5.The PMD rule Avoid SOQL queries inside loops should have the highest priority when running a static code analysis scan. How you can set this?Right Ans - Change the rule priority in the PMD Default RuleSet to 1.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

• / 3