Development-Lifecycle-and-Deployment-Architect Practice Test

A developer on the Universal Containers team has written a test class to test a method that involves a web service callout. Within the test class, the developer is supposed to load test data, create an instance of the Mock object, set the Test.setMock() to that Mock object, call startTest(), execute the code that makes the callout, call stopTest(), and compare the result with expectations. Unfortunately, the Developer forgot to use the Test.setMock() method step. What would happen when the developer runs this test class?

A. The test class fails without error message since the test class will simply skip the webservice callout during the execution.

B. The test class fails and the developer will see a message stating: Methods defined asTestMethod do not support Web service callouts.

C. The test class would make the web service callout and may or may not fail depending on the circumstances on the web service end

D. It is impossible to miss the Test.setMock() statement, the Developer Console will not let the developer save it since the test method callout

Universal Containers wants to implement a release strategy with major releases every four weeks and minor releases every week. Major releases follow the Development, System Testing (SIT), User Acceptance Testing (UAT), and Training Minor releases follow Development and User Acceptance Testing (UAT) stages. What represents a valid environment strategy consideration for UAT?

A. Minor releases use Partial copy and Major releases use Full copy

B. Minor and Major releases use separate Developer pro

C. Minor releases use Developer and Major releases Full copy

D. Minor and Major releases use the same Full copy.

Universal Containers has three types of releases in their release management strategy: daily, minor (monthly), and major (quarterly). A user has requested a new report to support an urgent client request. What release strategy would an Architect recommend?

A. Utilize the major release process to create the report directly in production bypassing the full sandbox.

B. Utilize the minor release process to create the report directly in production bypassing the full sandbox.

C. Utilize the major release process to create the report in a full sandbox and then deploy it to production.

D. Utilize the daily release process to create the report directly in a full sandbox and then deploy it to production.

At any given time, Universal Containers has 10 Apex developers building new functionality and fixing bugs. Which branching strategy should an Architect recommend that mitigates the risk of developers overwriting others changes?

A. Have all developers build new functionality in new branches, but fix bugs in the HEAD

B. Have all developers work in the same branch, continuously testing for regressions

C. Have developers work in separate branches and merge their changes in a common branch for testing

D. Don't use source control. Rely on Salesforce's built-in conflict detection mechanism

Universal Containers is working on the next phase of development for their Salesforce implementation involving a large amount of custom development. Which two strategies should be considered to address a critical production issue occurring in the middle of development? Choose 2 answers

A. Create separate branches for current development and production bug fixes and deploy the fix with current development when ready

B. Utilize one branch for both development and production bug fixes to avoid out-of-sync branches and simplify deployment

C. Utilize a source control system to allow separate branches for current development and production bug fixes

D. Refresh a sandbox for replication of the issue and testing the use -case scenarios once the code is fixed