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

（A）Refresh all non-preview sandboxes when the release management team has time.

（B）Contact support to roll back the release when Salesforce upgrades the sandboxes,

（C）No advice needed, mixing instance types is important for regression testing.

（D）Refresh all non-preview sandboxes during the release preview window.

（A）The deployment script will fail because the new field is not known for the previous API version 35.

（B）The deployment script will fail because the platform doesn't support the previous API version 35.

（C）The deployment script will pass because the new field is backward compatible with the previous API version 35.

（D）The deployment script will pass because the new field is supported on the current platform version.

（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）Create a sandbox from production to take the backup of existing metadata. To roll back deployment, manually delete new components and then deploy again to production using metadata from this sandbox.

（B）Backup the existing metadata using the ANT Migration Tool. To roll back deployment, deploy again to production using backed up metadata.

（C）Backup the existing metadata using ANT Migration Tool. To roll back deployment, manually delete new components and deploy again to production using backed up metadata.

（D）Create a sandbox from production to take the backup of existing metadata. To roll back deployment, use destructivechanges.xml to delete new components and then deploy again to production using metadata from this sandbox.

（A）Load Test

（B）Unit Test

（C）Performance Test

（D）Stress Test

（A）Developer Console

（B）Change Sets B

（C）ANT Migration Tool

（D）VS Code with Salesforce Extension

（A）Authorize to the Fullsandbox org; Validate with sfdximdapi:deploy; On successful validation, deploy with sfdx:mdapi:deploy

（B）Authorize to the Full sandbox org; Validate with sfdx:source:deploy; On successful validation, deploy with sfdx:source:deploy

（C）Authorize to the Full sandbox org; Validate with sfdx:mdapi:deploy; On successful validation, deploy with sfdx:source:deploy

（D）Authorize to the Full sandbox; validate with sfdx: source: deploy; On successful validation, deploy with sfdx;mdapi;deploy

（A）Implement the change in the sandbox, validate, and release to Production.

（B）Integration with the ERP system may not function as expected.

（C）Existing Apex test classes may start falling in Production.

（D）The change can be performed in Production, as it is a configuration change.

（A）Document deployment steps for any components that cannot be automatically deployed

（B）Generate and deploy a change set that enables the required settings

（C）Utilize the metadata API's deploy All Components call

（D）Generate and install a managed package that enables the required settings

（A）GitHub flow

（B）Leaf-based development

（C）Trunk-based development

（D）Scratch-org-based development

（A）Database management systems

（B）Issue tracking Tool

（C）Version control repository

（D）Middleware

（E）Continuous integration tool

（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）The testing of the JavaScript part of the Aura component can be tested in the Jest framework and the Apex controllers can be tested using test classes.

（B）The testing can be viewed in the lightning.force.com/c/jasminetests.app URL. The page loads and runs Jasmine test and writes pass/fail information to the screen.

（C）There is a $T test helper object that can be used to create the instance of the Lightning component, and it is promise enabled.

（D）Install the Lightning test service AppExchange package to enable the Aura component testing.

（A）All changes including hotfixes should be reviewed against security principles.

（B）No manual steps should be carried out.

（C）After deployment, the development team should test and verify functionality in production.

（D）Any production change should have explicit stakeholder approval.