Given a Customer Scenario, Describe and Recommend an Appropriate Testing Methodology. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   A Salesforce org uses a custom REST API to synchronize account data with an external ERP system. Which testing type verifies that the data exchange between Salesforce and the ERP system works correctly and maintains data consistency?

   • ASystem testing
   • BIntegration testing
   • CUser acceptance testing
   • DUnit testing
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   A Salesforce team is about to deploy a new Sales Cloud implementation. They want to validate that the entire system, including custom objects, workflows, and reports, works together to meet the business requirements. Which testing type should they perform?

   • AUnit testing
   • BUser acceptance testing
   • CIntegration testing
   • DSystem testing
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A bank is deploying Salesforce to manage customer accounts. The bank's security team wants to ensure that the Salesforce org is protected against common web vulnerabilities, such as cross-site scripting (XSS) and SQL injection. What should the team do?

   • AConduct load testing to ensure the system can handle the load
   • BPerform UAT with security-focused test cases
   • CReview the Salesforce security documentation and assume the org is secure
   • DConduct a penetration test on the Salesforce org
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   What is the typical outcome of a successful user acceptance testing (UAT) phase in a Salesforce project?

   • AAll defects are fixed
   • BBusiness stakeholders sign off on the solution
   • CIntegration tests pass
   • DCode coverage reaches 75%
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A Salesforce team is developing a custom Apex class that calculates discounts for a new product line. The class has complex logic with multiple branches. The team wants to ensure that future changes to the class do not break existing functionality. What should the team do to meet Salesforce's code coverage requirements and protect against regressions?

   • ACreate a test class that only verifies the happy path and deploy it to production
   • BUse the Developer Console to manually execute the class with various inputs before each release
   • CWrite a single Apex test method that calls the class with a representative input
   • DWrite Apex test methods that exercise all branches of the class and run them in every sandbox deployment
   Reveal Solution Discussion Select an answer first