- Email support@dumps4free.com
Universal Containers is validating an outbound change set from the Developer Sandbox to the production org. Which two locking behaviors will occur during a deployment? Choose 2 answers
A. The production org will be locked. Administrators cannot modify metadata during this time
B. The sandbox org will be locked. Administrators cannot modify metadata
C. The production org will be locked. Users can only Read data during this time
D. The production org will be locked. Users will still be able to Read/Write data to the org
Explanation:
A and D are the correct answers, as they are the locking behaviors that will occur during a deployment. A is correct, as the production org will be locked and administrators cannot modify metadata during this time, to prevent any conflicts or inconsistencies in the deployment. D is correct, as the production org will be locked and users will still be able to read/write data to the org, to minimize the impact on the business operations and user experience. B is incorrect, as the sandbox org will not be locked and administrators can still modify metadata, as the sandbox org is not the target of the deployment. C is incorrect, as the production org will not be locked and users can only read data during this time, as this would disrupt the business operations and user experience. You can learn more about the locking behaviors in the [Deploy Changes with Change Sets] unit on Trailhead.
Universal Containers (UC) have developed a managed package targeted for AppExchange. The product includes some Apex code to customize and create layouts. UC is in the testing phase of the package, so it's not certified yet. During testing on the target org, the Apex code for the layouts fails. Why are the Apex classes not able to access the metadata of the target org during testing?
A. Apex Settings to allow the access to metadata is not switched on.
B. UC needs to turn on Apex Settings within the custom metadata type.
C. The solution is flawed. UC should utilize the Tooling API from a web service call to modify the layouts.
D. UC needs to get the managed package certified by the Salesforce security review.
Explanation:
The reason why the Apex classes are not able to access the metadata of the target org during testing is that UC needs to get the managed package certified by the Salesforce security review. This is because Apex code in a managed package can only access the metadata of the target org if the package has passed the security review and has been granted the Modify Metadata permission. See Apex Metadata API for more details.
Universal Containers wants to delete the day’s test data in a partial copy sandbox every night, setting the sandbox back to a fresh state for tomorrows testing. The test data is approximately 1GB. What is the best strategy the architect should recommend?
A. Manually delete all records individually.
B. Execute a batch job that deletes all records created on the day.
C. Create a new developer copy sandbox every night.
D. Refresh the sandbox every night.
Explanation:
The best strategy to delete the day’s test data in a partial copy sandbox every night is to execute a batch job that deletes all records created on the day. This way, you can automate the process of cleaning up the test data and avoid manual work. Manually deleting all records individually is time-consuming and error-prone. Creating a new developer copy sandbox every night is unnecessary and wasteful, as developer copy sandboxes have limited storage and functionality. Refreshing the sandbox every night is also not feasible, as partial copy sandboxes have a refresh interval of 5 days.
A team of developers at Universal Containers has developed Apex Triggers and Apex Classes in a sandbox. The team has also written test classes to unit test these triggers and classes. When executed in the sandbox, all the test methods pass and all the classes meet the minimum code coverage requirement. But when they tried deploying these components to production, a few of these test methods failed What should an architect recommend?
A. Create test data in production before deploying the test classes
B. Set SeeAllData to True to use the data in production.
C. Explicitly set SeeAllData to True and generate data in test methods.
D. Do not use SeeAllData and generate data in the test methods
Explanation:
The best practice for writing test classes is to not use SeeAllData and generate data in the test methods. This ensures that the test classes are independent of the data in the org and can run successfully in any environment. Creating test data in production or setting SeeAllData to True can cause unexpected failures or data conflicts.
Universal Containers (UC) has four different business units (BUS) with different processes that share global customers. They have implemented a multi-org strategy with one org consolidating customer 360-degree view, and four orgs for the different BUS. Each of the BU orgs read and write customer information from/to the customer 360-degree view org in real time. UC is now launching a new BU that will use Salesforce. It does not share customers with the other BUS and needs flexibility in their Business processes. What should an architect recommend as org strategy for this new BU<br><br>
A. Use a new stand-alone Salesforce org for the new BU, not integrated with the others.
B. Deploy the new BU in customer 360-degree view org, and read and write customer information from it without need of custom integration.
C. Use the same Salesforce org of another BU that shares geographical localization with the new BU.
D. Use a new Salesforce org for the new BU, and customize integration so that it reads and writes customer information from the customer data org
Explanation:
The best option for the new BU is to use a new stand-alone Salesforce org, not integrated with the others. This will allow the new BU to have flexibility in their business processes, without affecting or being affected by the other BUs. Since the new BU does not share customers with the other BUs, there is no need to integrate with the customer 360-degree view org, which would add complexity and cost. Deploying the new BU in the customer 360-degree view org is not a good idea, as it would create confusion and duplication of data, as well as limit the customization options for the new BU. Using the same Salesforce org of another BU that shares geographical localization with the new BU is also not a good idea, as it would create conflicts and dependencies between the two BUs, as well as reduce the performance and security of the org. Using a new Salesforce org for the new BU, and customizing integration so that it reads and writes customer information from the customer data org is unnecessary and inefficient, as the new BU does not need to access or update the customer data of the other BUs.
| Page 11 out of 46 Pages |
| Previous |