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

（A）Skip the code review and focus on functional tests and UAT.

（B）Use static code analysis tool in the pipeline before manual code review.

（C）Choose the most senior developer to help the technical lead in the code review.

（D）Create development standards and train teams in those standards.

（A）Development environments should generally be refreshed after each working feature has been successfully migrated.

（B）Sandboxes should be refreshed on the day when the refresh is allowed for that type of sandbox.

（C）Production is the only pristine environment.

（D）Integration sandboxes should be refreshed rarely because of the burden of maintaining the various API.

（A）Modify the source org to allow an inbound connection to the target org

（B）Modify the source org to allow an outbound connection to the target org

（C）Modify the target org to accept an outbound connection from the source org

（D）Modify the target orgto accept an inbound connection from the source org

（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）Requirements Traceability Matrix

（B）Executive Leadership

（C）Business Continuity Plan

（D）Agile Methodology

（A）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.

（B）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.

（C）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.

（D）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.

（A）Continue development in a non -upgraded sandbox, and have the developer update the API version of the code to the upcoming API version for testing purposes

（B）Determine the developer sandbox upgrade schedule, and have the developer refactor the approach to the feature in the upgraded sandbox

（C）Continue with the current approach, since Salesforce will rectify the issue prior to updating the production environment to the new platform release

（D）Submit a request to Salesforce to enable the 'delay upgrade' feature in their org. Have the UC administrator schedule the upgrade for a later date

（A）Correcting the bug in UAT is ideal. Since UAT is a full copy, it will be the fastest location to fix and test the resolution.

（B）Since the issue was found in production, it should be treated as a change request and go into the backlog as an enhancement.

（C）UC should spin up a new sandbox to use as a hot fix environment. Once the bug is corrected, the change should beapplied to production and downstream environments.

（D）The fix should be made in the developer environment where the project work was done.
Once the fix has been made, it should go through a full deployment/testing process and adhere to the normal projectcadence.

（A）Use design Standards for Governance.

（B）Create a Center of Excellence with a charter document.

（C）Create a Release Management Process.

（D）Create project charters for each project.

（A）Use a combination of the Ant migration tool and change sets for deployment.

（B）Identify metadata dependencies, create logical groupings, and deploy in the right order.

（C）Use a continuous integration tool such as Jenkins to deploy in the right order.

（D）Sort and group the metadata alphabetically anddeploy them in the same order.

（A）Deliver working software, so if a software component is working, avoid changing it.

（B）Embrace change by working on a different scope every day.

（C）Create transparency by being honest and clear about timing, planning, and obstacles.

（D）Respect other teams by not doing their work (a developer should not test the software).

（A）Developers can observe their team velocity on the burn chart report in the agile tool.

（B）Developers can use the committed code's build status directly on the user story record.

（C）Developerscan collaborate and communicate effectively on specific user stories.

（D）Developers can see automated test statuses post code commit on a specific user story.

（A）Recommend fixing the issues in the development environment and deploying the changes to production.

（B）Recommend the customer team's proposal to fix the issues in the testing env and deploy them to production.

（C）Recommend fixing the issues in the test environment and migrating the changes to the development sandbox.

（D）Recommend fixing the issues in the development sandbox, migrating them to testing, and deploy to production after testing.

（A）Force.com IDE for minor releases and metadata API for major releases.

（B）Change sets for minor releases and metadata API for major releases.

（C）Change sets for minor releases and Force.com IDE for major releases.

（D）Change sets for both minor releases and major releases.

（A）Consult the metadata coverage report to identify features supported by packages.

（B）Test developed packages in test environments before installing to production.

（C）Move everything in the existing codebase to a single monolithic package.

（D）Version control does not need to be used, as packages manage all the code and configuration.

（A）Plan this an interim release after checking with Salesforce support.

（B）Plan this as a major release and align with a Salesforce major release.

（C）Plan this as a patch release and align with the Salesforce patch release.

（D）Plan this as a minor release with training and changemanagement.

（A）User Acceptance Testing

（B）Use of an Agile Methodology

（C）Requirements Traceability

（D）Automated Testing

（A）Session hacking

（B）SOQL injection

（C）Cross-site scripting

（D）CRUD/FLS (field level security)