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

（A）Create a design standard requiring integration to use declarative configurations patterns

（B）Create a governance framework focused on high-level business strategy and goals.

（C）Create a standard method for deprecating classes and fields using design standards.

（D）Create an adoption plan for end users using Salesforce dashboards and reports.

（E）Create a governance process requiring all projects to create project deliverable documentation.

（A）Use the same Salesforce org of another BU that shares geographical localization with the new BU.

（B）Deploy the new BU in customer 360-degree view org, and read and write customer information from it without need of custom integration.

（C）Use a new stand-alone Salesforce org for the new BU, not integrated with the others.

（D）Use a new Salesforce org for the new BU, and customize integration so that it reads and writes customer information from the customer data org

（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）Session hacking

（B）SOQL injection

（C）Cross-site scripting

（D）CRUD/FLS (field level security)

（A）Manually deploy and populate custom settings in production using a change set

（B）Create a custom metadata type and include this in your deployment to production

（C）Manually deploy and populate the custom settings in production prior to theApex Class deployment

（D）Script the deployment of all functionality via the Force.com Migration Tool

（A）The CURRENT API version must be used.

（B）PurgeOnDelete option must be set to TRUE.

（C）DestructiveChanges.xml file.

（D）Package.XML file.

（A）Can store code on a local machine, or a version control system.

（B）Can quickly deploy metadata using Execute Anonymous.

（C）Can create scratch orgs.

（D）Can Install application metadata from a central repository.

（E）Can use native Deployment Rollback Tool to quickly revert to prior state.

（A）Refresh a sandbox for replication of the issue and testing the use -case scenarios once the code is fixed

（B）Utilize a source control system to allow separate branches for current development and production bug fixes

（C）Utilize one branch for both development and production bug fixes to avoid out-of-sync branches and simplify deployment

（D）Create separate branches for current development and production bug fixes and deploy the fix with current development when ready

（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）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）Request a partial Sandbox copy after the next Salesforce release.

（B）Perform data masking on full sandbox after a refresh.

（C）Generate mock data that mimics production data shape and volume.

（D）Use Query Analyzer in production.

（A）Automated deployment

（B）Automated sandbox provisioning

（C）Automated change tracking

（D）Automated defect fixing

（A）Approve changes to project scope

（B）Design executive dashboards

（C）Determine project methodology

（D）Communicate project status