최신 Development-Lifecycle-and-Deployment-Architect 무료덤프 - Salesforce Certified Development Lifecycle and Deployment Architect

A. Multiple triggers on the same object, making it hard to understand the order of operations.

B. Duplicated logic across Visual force pages and Apex classes performing similar tasks.

C. Broken functionality due to Salesforce upgrades.

D. Custom-built JSON and String manipulation Classes that are no longer required.

E. Multiple unit test failures would be encountered.

A. Maintain separate developer branches for minor and major releases.

B. Maintain a single-entry point for production from the master branch.

C. Maintain unrestricted access to the release sandboxes for all changes being deployed.

D. Maintain a single repository for applications with individual branches for projects.

E. Automation is a must with various application branches in the repository.

A. Leave them to the Salesforce security review team, they would catch it if those are true problems.

B. Review the Checkmarx errors. If there is no need to fix, mark them as false positive and attach explanation, then submit.

C. Review the Checkmarx errors and fix all of them before submitting security review. Salesforce security review team will reject the request if any error remains.

D. Leave a partner support case, the partner manager will engage Salesforce support resources to help.

A. Create a sandbox refresh strategy to ensure each sandbox is refreshed every day.

B. Extract each permission set, commit and merge to source control, and run through CI checks.

C. Ask administrators to only make changes to profiles instead.

D. Advice developers to switch to SOSL queries that are more robust instead.

A. Ask administrators to run unit tests before every change.

B. Ensure a metadata backup is committed to version control every day and a diff published to the release team.

C. Stop administrators from making all changes.

D. Train the administrators to make their changes in a special "admin changes" sandbox, and then promote to production.

A. Utilize one branch for both development and production bug fixes to avoid out-of-sync branches and simplify deployment

B. Refresh a sandbox for replication of the issue and testing the use -case scenarios once the code is fixed

C. Create separate branches for current development and production bug fixes and deploy the fix with current development when ready

D. Utilize a source control system to allow separate branches for current development and production bug fixes

A. Use Salesforce-to-Salesforce to deploy the changes from Production to the sandbox, to ensure that changes made in production are reflected in the sandbox that the developers are working on

B. Manually replicate the same changes in the developer sandbox to ensure that changes made in production are reflected in the sandbox that the developers are working on

C. Refresh the developer sandbox to ensure that changes made in production are reflected in the sandbox that the developers are working on

D. Use a Change Set to deploy the changes from Production to the sandbox, to ensure that changes made in production are reflected in the sandbox that the developers are working on

A. In setup, switch both the Enable Dev Hub and Enable 2nd-Generation Managed Packages to Enabled.

B. In setup, switch the Enable Unlocked Packages and Second-Generation Managed Packages to Enabled.

C. In setup, switch the Enable Unlocked Packages to Enabled, keep the Enable Second-Generation Managed Packages as disabled.

D. In setup, switch the Enable Dev Hub to Enabled, then switch the Enable Source Tracking for Scratch Orgs to Enabled.

A. The first task of the new sprint must be the deployment approval. After that, the other tasks of the sprint can be performed in the environments and Git.

B. Commit upcoming changes to the features branch without merging into the develop branch. Deploy from the develop branch and then merge new sprint features into the develop branch.

C. Migrate the current code to the UAT sandbox. Begin new sprint development in the Dev sandbox.Make fixes in the UAT environment and deploy UAT for production after business approval.

D. Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.

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

B. Generate and install a managed package that enables the required settings

C. Generate and deploy a change set that enables the required settings

D. Utilize the metadata API's deploy All Components call

A. Using Lightning Web Components for every user interface.

B. Adopting user centered design to understand user needs before building the solution.

C. Sending weekly communication emails reporting on least engaged users

D. Stop development until current features start being used.

A. Have all developers work in the same branch, continuously testing for regressions

B. Don't use source control. Rely on Salesforce's built-in conflict detection mechanism

C. Have developers work in separate branches and merge their changes in a common branch for testing

D. Have all developers build new functionality in new branches, but fix bugs in the HEAD

A. Test

B. Continuous Integration

C. Change Sets

D. Build Release

E. Develop

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

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

C. Execute all test classes in sandboxes and select test classes in Production.

D. Test classes cannot be executed in sandboxes.

A. Minor changes do not need to be documented and can be made at any time.

B. Downstream environments will not be automatically updated when production changes.

C. All changes should still be tested.

D. Minor changes should be thoroughly documented and follow some type of standard cadence.

E. CI/CD is required in to successfully manage minor changes.

A. Designing a methodology that will meet a particular project's requirements

B. Enforcing that corporate project stage gates are part of the chosen methodology

C. Approving deviations from the chosen methodology, when required to address project issues

D. Setting the criteria for selecting Agile or Waterfall methodology to be used on internal projects