Articulate the Benefits, Limitations, Considerations, and Design Choices for a Solution Architecture and Handle Objections Related to the Design. TECHNICAL-ARCHITECT Practice Questions (Page 5)

Questions 21–22

1. 21application · medium

   A large retail client is adopting Salesforce for sales and service. During a design review, the CTO objects to the proposed integration architecture that uses middleware to synchronize customer data with the legacy ERP, arguing it adds latency and a single point of failure. The architect needs to address the objection while keeping the design intact. What is the most effective response?

   • APropose moving the middleware to a different cloud provider to reduce the latency, while keeping the current integration logic unchanged.
   • BAgree with the CTO and redesign the integration to use direct point-to-point calls between Salesforce and the ERP to eliminate the middleware entirely.
   • CAcknowledge the concern, explain the middleware provides decoupling, transformation, and retry capabilities that direct point-to-point calls lack, and propose a high-availability deployment for the middleware.
   • DExplain that the middleware is a standard pattern and the CTO should trust the architect's expertise, then continue the review without changes.
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A logistics company is planning to use Salesforce for field service scheduling. The proposed architecture relies on Salesforce's native scheduling capabilities. During a review, the operations director points out that the native scheduling does not support multi-day, multi-resource optimization. The architect needs to articulate the limitation and propose a design choice. What should the architect do?

   • AState that the limitation is acceptable because the company can manually adjust schedules in Salesforce after the native scheduler runs.
   • BExplain that the native scheduling can be customized with Apex to handle multi-day, multi-resource optimization, so no additional software is needed.
   • CRecommend moving the entire scheduling process to a legacy on-premises system and using Salesforce only for data storage.
   • DAcknowledge the limitation and propose integrating a third-party field service optimization engine that specializes in multi-day, multi-resource scheduling.
   Reveal Solution Discussion Select an answer first