- Email support@dumps4free.com
Universal Containers (UC) is implementing Service Cloud UC's contact center receives 100 phone calls per hour and operates across North America, Europe and APAC regions. UC wants the application to be responsive and scalable to support 150 calls considering future growth. what should be recommended test load consideration
A. Testing load considering 50% more call volume.
B. Testing load considering half the call volume.
C. Testing load considering 10xthe current call volume.
D. Testing load considering current call volume.
Explanation:
Testing load considering 50% more call volume is a reasonable test load consideration, as it can simulate the expected future growth and ensure that the application can handle the increased demand without compromising the performance or functionality.
Universal Containers (UC) is midway through a large enterprise project. UC is working in an agile model, and currently has four-week iterations, with a branching strategy supporting this approach. UC operates in a strict regulatory environment, and has dedicated teams for security, QA, and release management. The system is live with users, and a serious production issue is identified at the start of a sprint, which is narrowed down to a bug in some Apex code. Which three approaches should an architect recommend to address this bug? Choose 3 answers<br><br>
A. Investigate potential data impacts.
B. Fix the bug in a hotfix branch.
C. Wait until the next release to deploy the fix.
D. Attempt to fix the bug directly in production.
E. Seek stakeholder approval for the hotfix.
Explanation:
To address the bug in production, the architect should recommend the following approaches: Investigate potential data impacts, fix the bug in a hotfix branch, and seek stakeholder approval for the hotfix. Investigating the data impacts can help assess the severity and scope of the bug, and determine the best course of action to mitigate any data loss or corruption. Fixing the bug in a hotfix branch can help isolate the change and avoid introducing any other changes from the current sprint. Seeking stakeholder approval for the hotfix can help ensure compliance with the regulatory requirements and governance policies.
Universal Containers (UC) development team is developing a managed package for AppExchange. The product team has finished developing and testing, and wants to submit a Security Review. However, the product manager has concerns on the few errors from the Checkmarx code scanner. How should the product team proceed?
A. Review the Checkmarx errors. If there is no need to fix, mark them as false positive and attach explanation, then submit.
B. Leave them to the Salesforce security review team, they would catch it if those are true problems.
C. Leave a partner support case, the partner manager will engage Salesforce support resources to help.
D. Review the Checkmarx errors and fix all of them before submitting security review. Salesforce security review team will reject the request if any error remains.
Explanation:
The product team should review the Checkmarx errors and determine if they need to fix them or not. If the errors are false positives, meaning that they do not indicate a real security issue, the product team should mark them as such and attach an explanation, then submit the security review. This will help the Salesforce security review team to understand the rationale behind the code and avoid unnecessary rejections. The product team should not leave the errors to the Salesforce security review team, as they may reject the request if they find any potential security issue. The product team should not leave a partner support case, as this is not the proper channel for resolving code issues. The product team should not fix all the errors before submitting the security review, as some of them may not be relevant or critical, and fixing them may introduce new bugs or delays.
Universal Containers is about to begin the release of a major project. To facilitate this, they have several sandboxes to make their deployment train. These sandboxes are a mix of preview and non-preview instances. What should the architect recommend?
A. Refresh all non-preview sandboxes during the release preview window.
B. Refresh all non-preview sandboxes when the release management team has time.
C. No advice needed, mixing instance types is important for regression testing.
D. Contact support to roll back the release when Salesforce upgrades the sandboxes,
Explanation:
Refreshing all non-preview sandboxes during the release preview window is the best way to handle the situation of having a mix of preview and non-preview instances for the release of a major project. A release preview window is a period of time before a Salesforce seasonal release, where the customers can test their applications and integrations in a sandbox that has the same version as the upcoming release. By refreshing all non-preview sandboxes during this window, the architect can ensure that all the sandboxes are aligned with the same version and avoid any conflicts or errors during the deployment. Refreshing the sandboxes when the release management team has time, mixing instance types, or contacting support to rollback the release are not good practices, as they can cause inconsistency, confusion, or disruption in the release process.
Universal Containers is in the process of testing their integration between salesforce and their on-premise ERP systems. The testing team has requested a sandbox with up to 10,000 records in each object to benchmark the integration performance. What is the fastest approach anArchitect should recommend?
A. Spin off a partial copy sandbox using a sandbox template with all the objects required for testing the integration.
B. Spin off a Developer pro sandbox, migrate the metadata and load the data using data loader.
C. Spin off a full copy sandbox with all the objects that are required for testing the integration.
D. Spin off a Development sandbox, migrate the metadata and load the data using data loader.
Explanation:
The fastest approach to spin off a sandbox with up to 10,000 records in each object for testing the integration performance is to spin off a partial copy sandbox using a sandbox template with all the objects required for testing the integration. A partial copy sandbox can copy up to 10,000 records per object using a sandbox template that specifies the objects and fields to copy. A partial copy sandbox can also copy the metadata and the configuration settings from the production org. A developer pro sandbox, a development sandbox, or a full copy sandbox may not be able to copy enough data for testing the integration performance, as they have lower data storage limits. A developer pro sandbox and a development sandbox can only copy 1 GB of data, while a full copy sandbox can only copy 5 GB of data. A full copy sandbox may also take longer to spin-off, as it copies all the data and metadata from the production org.
| Page 4 out of 46 Pages |
| Previous |