Universal Containers CUC) is hiring offshore agile development teams to decrease costs and enhance UC's capability of delivering new features to its customers. However, the CTO Is not able to follow or measure the work of those teams. What should an architect recommend to increase transparency?
A. Schedule a daily stand-up meeting with representatives of all offshore teams to share the progress of the teams.
B. Request the offshore teams to send daily emails to the CTO with the progress of the teams.
C. Ask the offshore teams to add their progress and status in a shared spreadsheet.
D. A Request the offshore teams to share their work in progress in a virtual Kanban board tool.
Explanation:
A virtual Kanban board tool is a good way to increase transparency and collaboration among agile development teams, as it allows them to visualize their work, track their progress, and identify any bottlenecks or issues. A daily stand-up meeting, a daily email, or a shared spreadsheet are not as effective or efficient as a Kanban board tool.
Universal Containers is having trouble deploying metadata from SIT to UAT. UAT is complaining that it does not recognize some new Salesforce metadata types to be deployed. The deployment from Dev to SIT worked perfectly What could be the problem?
A. There is no problem, this is expected behavior.
B. UAT is on a preview release and SIT is not.
C. SIT is on a preview release and UAT is not.
D. Use the DX command line instead.
Explanation:
The problem is that UAT is on a preview release and SIT is not. A preview release is a version of Salesforce that contains the features and enhancements that will be available in the next major release. Preview releases are usually available a few weeks before the official release date, and they are assigned to a subset of instances. If UAT and SIT are on different instances, they may have different release versions, which can cause deployment issues. For example, if UAT has a preview release that contains some new metadata types that are not available in SIT, then deploying those metadata types from SIT to UAT will fail. To avoid this problem, the architect should check the Sandbox Preview Guide1 and the Release Notes2 to see if there are any changes that affect the deployment, and refresh and redeploy the sandboxes accordingly. There is a problem, and it is not expected behavior. Using the DX command line instead will not solve the problem, as it will still encounter the same version mismatch. SIT is not on a preview release and UAT is not, as that would not cause any deployment issues.
Universal Containers recently added a new sales division to ensure that Record Type IDs match both products migrating to Production, the Developer reports that Unit Tests are failing. What should an Architect do to ensure tests execute predictably?
A. Ensure that Record Type IDs match both Production and Sandbox orgs
B. Ensure executed Apex test run as valid users
C. Ensure unit tests generate their own test data
D. Ensure unit tests execute with see AllData=true
Explanation:
The best way to ensure that tests execute predictably is to ensure that unit tests generate their own test data, as this will avoid any dependency on the existing data or metadata in the org, which may vary across environments3. Option A is not correct, as ensuring that Record Type IDs match both Production and Sandbox orgs is not a reliable way to ensure test predictability, as Record Type IDs are not guaranteed to be the same across orgs, and may change due to refreshes or deployments4. Option B is not correct, as ensuring executed Apex test run as valid users is not a sufficient way to ensure test predictability, as valid users may have different permissions or profiles across orgs, and may not have access to the required data or metadata5. Option D is not correct, as ensuring unit tests execute with seeAllData=true is not a recommended way to ensure test predictability, as this will make the tests dependent on the existing data in the org, which may not be consistent or isolated.
Universal Containers has just completed several projects, including new custom objects and custom fields. Administrators are having difficulty maintaining the application due to not knowing how objects and fields are being used. Which two options should an Architect recommend? Choose 2 answers
A. Create Design standards to require help text on all custom fields and custom objects.
B. Create Design standards to consistently use the description field on custom objects.
C. Create Design standards with a document to store all custom objects and custom fields
D. Create Design standards to require all custom fields on all custom object page layouts
E. Create Design standards to consistently use the description field on custom fields.
Explanation:
Creating design standards to require help text on all custom fields and custom objects is an option that an Architect should recommend, as it helps to provide context and guidance for the administrators and users on how the fields and objects are used and what they mean. Creating design standards to consistently use the description field on custom fields is also an option that an Architect should recommend, as it helps to document the purpose and function of the fields and make them easier to maintain and understand. Creating design standards to consistently use the description field on custom objects is not an option that an Architect should recommend, as it is not a mandatory field and may not provide enough information for the administrators. Creating design standards with a document to store all custom objects and custom fields is not an option that an Architect should recommend, as it may be difficult to keep the document updated and synchronized with the actual metadata in the org. Creating design standards to require all custom fields on all custom object page layouts is not an option that an Architect should recommend, as it may clutter the user interface and reduce the usability and performance of the application.
Northern Trail Outfitter’s development team has built new features for its sales team in the Asia-Pacific region. While testing the Apex classes, the developers are constantly hitting the governor limits. What should the architect recommend during the review to address this issue?
A. Use test.startTest() and test.stop Test() methods to reset governor limits.
B. Use an AppExchange product which can temporarily increase the governor limits.
C. Use the auto reset property to automatically reset governor limits during off-hours.
D. Use test.setLimit() and test.resetLimit() methods to reset governor limits.
Explanation:
The best way to address the issue of hitting governor limits while testing Apex classes is to use test.startTest() and test.stopTest() methods to reset governor limits. These methods mark the start and end of the test code, and allow you to run your test code with a separate set of governor limits. There is no AppExchange product that can temporarily increase the governor limits, and there is no auto reset property or test.setLimit() and test.resetLimit() methods that can reset governor limits.
Page 8 out of 46 Pages |
Previous |