Development-Lifecycle-and-Deployment-Architect 無料問題集「Salesforce Certified Development Lifecycle and Deployment Architect」

（A）Leads, Accounts, Contacts, Products, Opportunities, Opportunity Line Items

（B）Accounts, Contacts. Opportunities, Products, Opportunity Line Items, Leads

（C）Leads, Contacts, Accounts, Opportunities, Products, Opportunity Line Items

（D）Accounts, Contacts, Leads, Products, Opportunities, Opportunity Line Items

（A）Use change sets for deploying all the unsupported components.

（B）Use AppExchange products to deploy unsupported components.

（C）Deploy unsupported components manually before/after deployment.

（D）Use the force.com IDE for deploying the unsupported components.

（A）One month before go -live, deploy to Staging and to Production Support. Deploy from Production Support to Production at go-live

（B）Two weeks before go -live, deploy to Staging and then refresh the Staging and Production support sandboxes. Deploy from Staging to Production at go-live

（C）Approximately six weeks before go -live, ensure the sandbox will be on the release preview. One week before go live, deploy to Staging. Deploy from Staging to Production at go-live

（D）One week before go -live, initiate the Staging sandbox refresh and then immediately deploy to Staging.Deploy from Staging to Production at go-live

（A）Custom Field

（B）CustomObject

（C）CustomMetadataType

（D）CustomMetadata

（A）Package development model, because it allows packages to be created and deployed using declarative (point-and-click) development tools, without writing code.

（B）Package development model, so teams can build release artifacts that can be tested and released independently from artifacts for other projects.

（C）Org development model, because the acquired company's team is already using it, and it is better than the change set development model.

（D）Change set development model, because UC is already using it, so it will face less resistance.

（A）Refresh a Developer Pro sandbox every weekend and include an appropriate sandbox template.

（B）Refresh a Developer Pro sandbox every weekend and load data needed using data loader.

（C）Refresh a Partial Copy sandbox every weekend and include an appropriate sandbox template.

（D）Refresh a Partial Copy sandbox every weekend and load data needed using data loader.

（A）Developers work off of the Feature branch, which is pulled from the Master branch and the Feature branch is then merged with the Develop branch.

（B）Developers work off of the Feature branch, which is pulled from the Release branch, and the Feature branch is then merged with the Develop branch.

（C）Developers work off of the Feature branch, which is pulled from the Develop branch, and the Feature branch is then merged with the Hotfix branch.

（D）Developers work off of the Feature branch, which is pulled from the Develop branch, and the Feature branch is then merged with the Develop branch.

（A）The test class would make the web service callout and may or may not fail depending on the circumstances on the web service end

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

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

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

（A）Build Release

（B）Develop

（C）Test

（D）Continuous Integration

（E）Change Sets

（A）Provide the Release Management team a copy of the audit trail from the sandbox you wish to deploy from

（B）Provide a spreadsheet of all components and utilize the metadata API's read Metadata call

（C）Send a package.xml file with associated metadata in a .zip file to the Release Management team

（D）Create a change set in each sandbox and download the package.xml file for the release management team

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

（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 directly in production bypassing the full sandbox.

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

（A）Create a Center of Excellence for release management.

（B）Execute regression testing before code can be committed.

（C）Use static code analysis to enforce coding standards.

（D）Require pull requests to be reviewed by two developers before merging.

（A）Automated tests should be run when branches are merged.

（B）Automated tests should be run dally in all Developer Orgs.

（C）Automated tests should be run daily in all Developer Orgs, and when branches are merged.

（D）Automated tests should be run only when merging into Full or Partial Copy sandboxes.

（A）AuraDriver Test

（B）JSTEST

（C）ACCTEST

（D）WebDriver Test