Universal Containers (UC) maintains its Salesforce org using its internal tools and processes for managing its application lifecycle. The UC team has been facing challenges on their development processes in their recent two releases. The architect has recommended the UC team to follow the org development model to address the challenges faced. Which two characteristics of the org development model will help UCaddress the challenges? Choose 2 answers
A. Automated deployment
B. Automated defect fixing
C. Automated sandbox provisioning
D. Automated change tracking
Explanation:
The org development model is a traditional approach that uses sandboxes as the primary development environments. It relies on tools such as change sets, the Ant Migration Tool, or the Metadata API to deploy changes between orgs. One of the benefits of this model is that it allows automated deployment, meaning that the deployment process can be scripted and executed without manual intervention. This can save time and reduce errors. Another benefit of this model is that it allows automated sandbox provisioning, meaning that the creation and configuration of sandboxes can be done programmatically using the Sandbox API or the Salesforce CLI. This can help maintain consistency and alignment across different environments. Automated defect fixing and automated change tracking are not characteristics of the org development model, but rather of the package development model, which uses source code as the source of truth and supports source tracking and automated testing.
Universal Containers has a highly integrated environment with significant process orchestration between systems. When refreshing UAT, Objects that have external Ids from Production no longer point to valid External Ids in the UAT environment. What should an Architect do to resolve this?
A. Let UAT point to production integrations and rollback each transaction after it finishes.
B. Delete all the data and use an Automated testing tool to create new data across all the systems in UAT.
C. Mask the External Id so nobody can see the production value.
D. In the post refresh plan, modify external ids to a known valid set of values for UAT.
Explanation:
In the post refresh plan, modifying external ids to a known valid set of values for UAT is the best way to resolve the issue of objects that have external ids from production no longer pointing to valid external ids in the UAT environment. This way, the data integrity and consistency across the integrated systems can be maintained. Letting UAT point to production integrations and rolling back each transaction after it finishes is not a good practice, as it can cause data loss or corruption in production. Deleting all the data and using an automated testing tool to create new data across all the systems in UAT is not feasible, as it can take a lot of time and resources. Masking the external id so nobody can see the production value is not a solution, as it does not address the underlying problem of invalid references.
Universal Containers (UC) is considering updating their Salesforce Release Management process. Which three best practices should UC consider for Release Management? Choose 3 answers
A. Design the right sandbox strategy for the release.
B. Release sign-off is only required for Production.
C. Regression testing is mandatory for each release.
D. Maintain a pre/post deployment checklist for each release.
E. Publish a release calendar for each phase of the release.
Explanation:
Designing the right sandbox strategy for the release is a best practice, as it helps to ensure the quality and consistency of the code/configuration across different environments. Regression testing is mandatory for each release, as it helps to verify that the existing functionality is not broken by the new changes. Maintaining a pre/post deployment checklist for each release is a best practice, as it helps to track the tasks and dependencies for each deployment. Release sign-off is not only required for Production, but also for other environments such as UAT and Staging. Publishing a release calendar for each phase of the release is not a best practice, as it may change due to unforeseen circumstances and create confusion.
What are three advantages of the package development model? Choose 3 answers
A. Improving team development and collaboration.
B. Eliminating the need of using change set, which should no longer be used as it can get messy working with package development models.
C. Facilitating automated testing and continuous integration.
D. Significantly reducing the need for manually tracking changes.
E. Providing its own source control, so the source can be deployed In any sandbox orgs.
Explanation:
The advantages of the package development model are improving team development and collaboration, facilitating automated testing and continuous integration, and significantly reducing the need for manually tracking changes. The package development model allows the developers to work on modular and reusable components that can be easily tested and deployed. The package development model does not eliminate the need of using change sets, as they can still be used for deploying non-packaged components or metadata. The package development model does not provide its own source control, but rather relies on external source control systems such as Git.
Universal Containers has multiple minor and major releases in a year. Minor releases have sample configuration changes, while major releases involve large number of complex code components. What deployment tools should an architect recommend for both types of releases?
A. Change sets for minor releases and Force.com IDE for major releases.
B. Change sets for both minor releases and major releases.
C. Change sets for minor releases and metadata API for major releases.
D. Force.com IDE for minor releases and metadata API for major releases.
Explanation:
Change sets for minor releases and metadata API for major releases is the best deployment tool recommendation for both types of releases. Change sets are a native Salesforce tool that allows the team to deploy configuration changes between connected orgs. They are suitable for minor releases that have simple configuration changes, such as adding fields, objects, or workflows. Metadata API is a more advanced tool that allows the team to deploy both configuration and code changes between any orgs. It is suitable for major releases that have large number of complex code components, such as Apex classes, triggers, Visualforce pages, or Lightning components.
The CEO at Universal Containers (UC) is receiving constant complaints from business stakeholders that the development teams are not frequently delivering value to the end-user. The CEO talked with the CTO, who argues the opposite, explaining that the development teams are delivering value every Sprint. The architect suggests to the CTO to implement Kanban to solve this disagreement. How can Kanban help clarify whether value is being delivered to the business?
A. Kanban teams respond to unplanned work and changes by dropping everything and jumping on the new request, ensuring agility.
B. Kannan traits includes metrics, like lead time and throughput, which increases transparency.
C. Kanban can make use of the Salesforce Agile Accelerator to speed up delivery.
D. Kanban limits work in progress, so the executives will know the development team is not overworked.
Explanation:
Kanban can help clarify whether value is being delivered to the business by using metrics, like lead time and throughput, which increase transparency. Lead time measures how long it takes to complete a work item from the time it is requested, and throughput measures how many work items are completed in a given time period. These metrics can help the business stakeholders see the progress and performance of the development teams, and align their expectations with the reality.
Kanban does not respond to unplanned work and changes by dropping everything and jumping on the new request, as this would disrupt the flow and quality of work. Kanban does not make use of the Salesforce Agile Accelerator, as this is a tool for managing agile projects. Kanban does limit work in progress, but this is not the main reason why it can help clarify whether value is being delivered to the business.
Universal Containers (UC) is planning to move to Salesforce Sales Cloud and retire its homegrown on-premise system. As part of the project, UC will need to migrate 5 million Accounts, 10million Contacts, and 5 million Leads to Salesforce. Which three areas should be tested as part of data migration? Choose 3 answers
A. Lead assignment
B. Data transformation against source system
C. Contact association with correct Account
D. Account and Lead ownership
E. Page layout assignments
Explanation:
Three areas that should be tested as part of data migration are: data transformation against source system, contact association with correct account, and account and lead ownership. These areas can help ensure that the data is migrated correctly and accurately, and that the relationships and ownership are preserved. Lead assignment is not an area that should be tested as part of data migration, as it is a business process that is triggered after the data is migrated. Page layout assignments is also not an area that should be tested as part of data migration, as it is a configuration setting that is independent of the data. See Data Migration for more details.
What two things are needed to delete metadata with a deploy() call?= Choose 2 answers
A. Package.XML file.
B. The CURRENT API version must be used.
C. DestructiveChanges.xml file.
D. PurgeOnDelete option must be set to TRUE.
Explanation:
To delete metadata with a deploy() call, two things are needed: a package.xml file and a destructiveChanges.xml file. The package.xml file specifies the API version and the components to be deployed, while the destructiveChanges.xml file specifies the components to be deleted. The API version does not have to be the current one, as long as it is compatible with the components. The purgeOnDelete option is not required, as it only determines whether the deleted components are stored in the recycle bin or not.
Universal Containers has five development teams. The performance of the teams has been good, but the number of bugs has been increasing. After each sprint, they need more time to understand the code and make changes. What are two ways to improve the performance? Choose 2 answers
A. Define a team that will analyze/approve all changes.
B. Define and follow code standards.
C. Sprint review process.
D. Version control system to identify who is generating the bugs.
Explanation:
To improve the performance of the development teams, the following ways can be suggested: Define and follow code standards, and implement a sprint review process. Code standards can help ensure consistency, readability, and maintainability of the code, as well as reduce errors and bugs. A sprint review process can help evaluate the work done in each sprint, demonstrate the functionality, and gather feedback from the stakeholders and users.
Universal Containers (UC) has recently acquired other companies that have their own Salesforce orgs. These companies have been merged as new UC business units.
The CEO has requested an architect to review the org strategy, taking into consideration two main factors:
• The CEO wants business process standardization among all business units.
• Business process integration is not required as the different business units have different customers and expertise.
Which org strategy should the architect recommend in this scenario, and why?
A. Single-org strategy, as the high level of business process standardization will be easier to implement in a single org.
B. Multi-org strategy, as it is uncommon for the diversified business units to get used to working in the same space as the other business units.
C. A Multi-org strategy, as they could deploy a common managed package into the orgs of the different business units.
D. Single-org strategy, as costs increase as the number of orgs go up.
Explanation:
A single-org strategy is the best option for UC, as it will enable them to achieve business process standardization among all business units, which is the main goal of the CEO. A multi-org strategy would make it harder to enforce consistent processes and policies across the different business units, and would also increase the costs and complexity of managing multiple orgs. A common managed package could help with some aspects of standardization, but it would not cover all the possible scenarios and customizations that UC might need.
| Page 9 out of 23 Pages |
| Previous |
Copyright © - All Rights Reserved