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

（A）Create a Center of Excellence Charter document.

（B）Create a backup system using GIT Repositories.

（C）Create a Release Management process.

（D）Create Design Standard for Governance.

（A）UC should hire a partner to complete the needed backlog items.

（B）UC should eliminate low-value items from the backlog.

（C）UC should start a citizen development program.

（D）UC should hire additional resources to reduce the backlog.

（A）Define and follow code standards.

（B）Define a team that will analyze/approve all changes.

（C）Sprint review process.

（D）Version control system to identify who is generating the bugs.

（A）Whether Salesforce will wait to upgrade the pod until after a UC release is complete.

（B）How to roll back to the previous Salesforce release if there are issues.

（C）When to test a new UC feature release if there are issues.

（D）How to test existing functionality to ensure no regressions are introduced.

（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）Eliminating the need of using change set, which should no longer be used as it can get messy working with package development models.

（B）Significantly reducing the need for manually tracking changes.

（C）Improving team development and collaboration.

（D）Providing its own source control, so the source can be deployed In any sandbox orgs.

（E）Facilitating automated testing and continuous integration.

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

（B）Execute all test classes in sandboxes and select test classes in Production.

（C）Test classes cannot be executed in sandboxes.

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

（A）All metadata changes for the release.

（B）Changes to components not yet supported by source tracking.

（C）No manual tracking required. All changes are automatically tracked.

（D）Only the changes made via the Setup UI.

（A）Change managers

（B）Scrum master

（C）Product owner

（D）Release managers

（A）Reporting project status, timelines, and impacts

（B）Communication to stakeholders on a "need -to -know" basis

（C）Consistent communication to a pre -defined list of stakeholders

（D）Requesting feedback for outstanding architectural questions

（A）Kanban limits work in progress, so the executives will know the development team is not overworked.

（B）Kanban teams respond to unplanned work and changes by dropping everything and jumping on the new request, ensuring agility.

（C）Kannan traits includes metrics, like lead time and throughput, which increases transparency.

（D）Kanban can make use of the Salesforce Agile Accelerator to speed up delivery.

（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）Partner development org offers more storage.

（B）Partner development org never expires.

（C）Partner development org has a greater number of licenses available for the team.

（D）Only partner development org supports managed beta testing.

（E）Partner development org offers higher API limit.

（A）Minor and Major releases use separate Developer pro

（B）Minor releases use Developer and Major releases Full copy

（C）Minor and Major releases use the same Full copy.

（D）Minor releases use Partial copy and Major releases use Full copy

（A）Create a spreadsheet of metadata changes and reconcile the overlaps.

（B）Share the test plans between the teams on each release type.

（C）Gate all release decisions at the center of excellence.

（D）Create a release calendar, train and align all the teams.

（A）Developer Edition

（B）Developer sandbox

（C）Developer Pro sandbox

（D）Partner Developer Edition

（A）Set up Salesforce-to-Salesforce to deploy the functionality from one org to the other

（B）Create a package in a Developer Edition org and deploy it to both production orgs

（C）Develop the functionality in a sandbox and deploy it to both production orgs

（D）Create a managed package in a sandbox and deploy it to both production orgs