Universal Containers (UC) is implementing a Salesforce project with large volumes of data and daily transactions. The solution includes both real-time web service integrations and Visualforce mash -ups with back -end systems. The Salesforce Full sandbox used by the project integrates with full-scale back -end testing systems. What two types of performance testing are appropriate for this project? Choose 2 answers
A.
Pre -go -live automated page -load testing against the Salesforce Full sandbox.
B.
Post go -live automated page -load testing against the Salesforce Production org.
C.
Pre -go -live unit testing in the Salesforce Full sandbox.
D.
Stress testing against the web services hosted by the integration middleware.
A.
Pre -go -live automated page -load testing against the Salesforce Full sandbox.
D.
Stress testing against the web services hosted by the integration middleware.
Explanation:
A (Pre-go-live automated page-load testing) ensures that Visualforce mashups and Salesforce UI pages perform efficiently before launching to production.
D (Stress testing against web services) validates system robustness under real-world load scenarios for middleware and integrations.
Unit testing (option C) ensures logic correctness but doesn't evaluate actual performance under real conditions. Post go-live testing (option B) risks identifying performance issues after users have already experienced negative impacts. Pre-go-live automated page-load tests and middleware stress tests proactively ensure systems perform under realistic conditions, making these the appropriate types of performance tests.