Universal Containers is adopting Scrum as an agile methodology and wants to choose a software tool to support the adoption.
What three key features of an agile development support tool should an architect look for? (Choose three.)
Universal Containers is adopting Scrum as an agile methodology and wants to choose a software tool to support the adoption.
What three key features of an agile development support tool should an architect look for? (Choose three.)
When choosing a software tool to support the adoption of Scrum, the key features to look for include: work assignment, which enables the team to distribute user stories or tasks effectively; sprint backlog management, which is essential for organizing and tracking the progress of tasks within a sprint; and product backlog prioritization, which helps in managing the list of all desired work on the project and setting priorities. While features like a Kanban board and email notifications can also be useful, they are not as critical to the core functionalities needed for agile development as the mentioned three features.
Universal Containers (UC) is looking for advice on how often it should refresh its sandboxes. UC currently uses a development lifecycle that starts with developer environments and moves to integration testing, QA testing, UAT, and then production. They have many scrum teams working concurrently and the teams do not agree on when refreshes should occur.
What two recommendations should the architect suggest? (Choose two.)
Sandboxes should be refreshed on the day when the refresh is allowed for that type of sandbox to ensure they stay up-to-date with the latest changes and maintain environment consistency. Development environments should generally be refreshed after each working feature has been successfully migrated to ensure that the developers are working with the most recent and relevant data, which aligns with best practices for continuous integration and development. This approach also helps avoid conflicts and ensures smooth development progress.
Universal Containers has seven orgs in different regions. Its processes are global and standardized but each region needs the flexibility to be able to understand the global code and customize some aspects for its regions.
Which development model is optimized for this need?
Use unlocked packages to deploy the global code and allow each country to create its customized unlocked package extensions is suitable for Universal Containers' need to maintain standardized global processes while allowing flexibility for regional customization. By using unlocked packages, the global code can be maintained and deployed universally, and individual regions can extend this code through additional unlocked packages to meet their unique requirements. This approach balances global coherence with regional adaptability.
Universal Containers (UC) is on the Unlimited Edition of Salesforce orgs. Currently there are four Developer Pro sandboxes used by dev teams for various purposes, one partial copy sandboxes used for training, one full sandbox used for user acceptance testing. There is another full sandbox used for performance testing during the initial launch, and it is no longer being actively used.
A system administrator had reported yesterday that none of the sandboxes can be refreshed.
What is the most probable action an architect can help the system administrator with?
Universal Containers has an unused full sandbox that can be deleted to free up resources. Since they are on the Unlimited Edition, they should ideally have enough sandboxes for their needs, but currently have an excess full sandbox that is not being used. Deleting the full sandbox used for performance testing, which is no longer active, would likely resolve the issue and allow the other sandboxes to be refreshed.
Sales and Service products will be created by two teams that will use second-generation managed package(s). The Sales team will use a specific function of the Service product, but the architect wants to ensure that this team will only use the functions exposed by the Service team. No other team will use these same functions.
What should an architect recommend?
The best approach is to create two second-generation managed packages with the same namespace and set the methods that should be shared with the @namespaceAccessible annotation. This approach ensures that only the Sales team can access the specific functions exposed by the Service package while maintaining the isolation and reusability of both packages. The @namespaceAccessible annotation is specifically designed for scenarios where certain methods need to be accessed by packages within the same namespace.