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

（A）Define a brand-new custom object with a picklist field to host all of the service centers.

（B）Add all of the service centers to a custom metadata type.

（C）Add the service centers to a hierarchical custom settings.

（D）Add the service centers to a list custom settings.

（A）Requirements Traceability Matrix

（B）Change Control Board

（C）Project ManagementOffice

（D）Center of Excellence

（A）Load Test

（B）Unit Test

（C）Performance Test

（D）Stress Test

（A）Design theright sandbox strategy for the release.

（B）Publish a release calendar for each phase ofthe release.

（C）Release sign-off is only required for Production.

（D）Maintain a pre/post deployment checklist for each release.

（E）Regression testing is mandatory for each release.

（A）Perform code reviews before promoting to a pre -production sandbox

（B）Act as a backup in case of catastrophic data loss

（C）Create a branching strategy that tracks each feature or change separately

（D）Keep a history of changes made by each developer

（E）Automatically deploy changes from sandbox to production

（A）A burndown chart showing team finishes early sprint after sprint

（B）The definition of done (DoD)

（C）A burndown chart showing the team misses their forecast sprint after sprint

（D）A Kanban board showing there's always the maximum allowed amount of work in progress (WIP)

（A）Active Process Builders

（B）Validation Rules

（C）Workflow Rules

（D）Case Assignment Rules

（A）Ensure all code that is being deployed is checked into source control

（B）Upload a change set from sandbox to production as early as possible

（C）Validate the final deployment package against production prior to go-live

（D）Create a new sandbox and perform a test deployment to that environment

（A）Wave

（B）Port management tool

（C）Spreadsheets

（D）Code Repository

（A）Opt for Single-org strategy, standardized sales process, common rules, and business unit-specific locale

（B）Opt for Multi-org strategy, each org have its own sales process, common rules and operate in locale

（C）Opt for Single-org strategy, standardized sales process, common rules, and same locale for all business units.

（D）Opt for Multi-org strategy, standardized sales process, common rules, and same locale across orgs.

（A）Changes Sets cannot be used to deploy from Developer Edition to Production which will make deployment morecomplex

（B）Developer Edition orgs have limited user counts and low data volume limits, which will make User Testing difficult.

（C）Developer Edition orgs do not run on production servers and will not perform well during testing.

（D）Developer Edition orgs cannot have sandboxes,which will make team development difficult.

（E）Code changes cannot be deployed from a Developer Sandbox 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）Implement a comprehensive DevOps framework for all initiatives within Universal Containers

（B）Establish a global Center of Excellence to define and manage Salesforce development standards across the organization

（C）Implement a project management tool to manage all change requests on the project

（D）Identify relevant Stakeholders from within Universal Containers to obtain governance goals and objectives

（A）It is a shared environment

（B）It causes Internetcongestion

（C）There is not enough CPU

（D）It is blocked by data center infrastructure

（A）Execute all test classes in sandboxes and selected test classes in Production.

（B）Do not execute test classes in sandboxes and all test classes in Production.

（C）Test classes cannot be executed in sandboxes.

（D）A Do not execute any test classes in sandboxes andProduction.

（A）Include fixes for critical bugs in the ongoing Development sandboxes so that they will be released with the other code.

（B）Keep teams separate until the end of the project and create a Full Copy sandbox to merge their work then.

（C）Utilize a dedicated developer pro sandbox to address critical bugs and release to production.

（D）Address critical bugs in the Development sandboxes and push those changes to production separately.

（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