Summer Special Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: exc65

Rob, would like to enforce the following quality gates when deploying to INT:

* A static code analysis for all Apex classes and triggers.

* A validation deployment for all Apex classes and triggers.

* A validation deployment for profiles.

What is the easiest way for him to address these requirements?

A.

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.

B.

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.

C.

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.

D.

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

A developer has deployed a user story from a Dev sandbox that contains an old version of the code. While deploying, the auto-resolution engine has overwritten the most up-to-date version of the code in UAT. How can you prevent this from happening again in the future?

A.

Commit the code again before deploying.

B.

Resolve the conflict manually using the Online Conflict Resolution.

C.

Change the user story base branch to 'Dev'

D.

All are correct.

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?

A.

Set the rule violation score in the PMD Default RuleSet to 1.

B.

Change the rule priority in the PMD Default RuleSet to 1. (I think this is correct as priority start from 1 still we need to check in PMD doc)

C.

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

D.

Create a new rule and set the priority to Blocker. Then, add it to the Default RuleSet.

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.

You have created two different Account page layouts in Dev1, one for sales reps and and another one

for the support team. You have committed the two page layouts on a user story and you are ready to

deploy them to the next environment. However, the sales manager makes a last-minute decision for

his team to continue using the standard Account page layout for now. What is the easiest way to

prevent the sales reps layout from being deployed while deploying the support team layout?

A.

Delete the user story, create a new one and commit just the layout for the support team.

B.

Use the Recommit Files Git operation, flag the Create New Feature Branch checkbox and select only the layout for the support team.

C.

Use the Recommit Files Git operation, flag the Re-Create Feature Branch checkbox and select only the layout for the support team.

D.

Go to the user story and use the Destructive Changes Git operation to delete the sales reps layout. Then, use Commit Changes and just commit the layout for the support team.

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? Select all that apply!

A.

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.

B.

The promotion test level on the user story was set to NoTestRun.

C.

The test level in the Promotion record was set to RunLocalTests in previous deployments.

D.

The test level in the Promotion record was set to RunAllTests in previous deployments.

Why the commits on a user story could display the status Commit not in branch?

A.

The committed component had no changes compared to the master branch.

B.

Someone has deleted the commits directly in the feature branch.

C.

The commit process failed.

D.

Someone has used the Re-Create Feature Branch on the user story

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

Dave comitted 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?

A.

Manually promote and remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Promotion record.

B.

Manually promote and add ApexClass to the Exclude From Autore Solve multi-select picklist field in the Promotion record.

C.

Remove ApexClass from the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.

D.

Add ApexClass to the Exclude From Auto Resolve multi-select picklist field in the Pipeline record.

Which of the following examples could potentially create a Git conflict?

A.

Merge the release branch into the destination branch.

B.

Merge the feature branch into the source org's branch.

C.

Merge the feature branch into the promotion branch.

D.

B and C.