Salesforce Development Lifecycle and Deployment Designer Certification Questions With 100% Correct Answers!!

Center of Excellence (CoE) - Answer-A few stakeholders from different functional groups work together to ensure that changes support business goals and follow IT best practices and processes. Release Management Team - Answer-Responsible for planning, scheduling, and controlling the build, in addition to testing and deploying Releases Governance Framework - Answer-Improves coordination by ensuring all members of your team are working together to achieve project deadline Design Standards - Answer-Follow key standards for coding, testing, integration, large data volumes, and other areas that affect the services you share with other Salesforce customers. Change Control Board - Answer-Committee that makes decisions regarding whether or not proposed changes to a software project should be implemented Executive Sponsor - Answer-Champions the project by acting as the project's highest level change leader - communicates the importance to stakeholders and senior leadership; obtains go-ahead decision and collaboration; is accountable for success; exercise strategic control to achieve project objectives and business benefits. Architecture Review Board - Answer-They will be responsible for defining the overall structure of a program or a system. They will also be overseeing IT assignments that are aimed at improving the business and ensuring that all parts of the project run smoothly. Steering Committee - Answer-Steering committee is a group of high-level advisers who have been asked to govern an organization or organizational segment and provide it with direction. Charter - Answer-Goals and the strategies to achieve with Salesforce. A clear charter helps the team to prioritize requirements, to focus on the area that meets their business goals as quickly as possible.Release Categories: Daily - Answer-Bug fixes and simple changes that do not require formal release management, including reports, dashboards, list views, email templates, and user administration. Minor - Answer-Changes with limited impact, such as a new workflow rule or trigger impacting a single business process. These releases typically require testing, but limited training and change management, and are delivered within a few weeks. Major - Answer-Changes with significant impact, including configuration and code changes with one or more dependencies. Because these releases greatly affect the user experience and data quality, they require thorough testing, training, and careful change management. Major releases typically occur once a quarter (or like Salesforce, three times a year). Releasing on the same day of the week for minor and major releases is a best practice. This allows for company-wide planning and sets expectations with your business users. In addition, don't schedule releases near holidays or other major events. Production Development Cycle - Answer-1. Plan functional requirements. 2. Develop using Salesforce Web tools, using profiles to hide your changes until they're ready to deploy. 3. Update profiles to reveal your changes to the appropriate users. 4. Notify end users of changes Sandbox Development Cycle - Answer-1. Create a development environment. 2. Develop using Salesforce Web and local tools. 3. Test within the development environment. 4. Replicate production changes in the development environment. 5. Deploy what you've developed to your production organization. Development Cycle for Isolated Development and Testing - Answer-1. Create a development environment. 2. Develop using Salesforce Web and local tools. 3. Create a testing environment. 4. Migrate changes from development environment to testing environment. 5. Test. 6. Replicate production changes in other environments.7. Deploy what you've developed to your production organization Development Cycle for Multiple Projects with Integration, Testing, and Staging - Answer-1. Create development environments. 2. Develop using Salesforce Web and local tools. 3. Create testing environments, including UAT and integration. 4. Migrate changes from development environment to integration environment. 5. Test. 6. Migrate changes from integration environment to UAT environment. 7. Perform user-acceptance tests. 8. Migrate changes from UAT environment to staging environment. 9. Replicate production changes in staging environment. 10. Schedule the release