Given a Scenario, Describe the Architectural Considerations When Planning, Defining, or Working Within a Single or Multi-Org Environment. TECHNICAL-ARCHITECT Practice Questions (Page 1)

Questions 1–5

1. 1application · medium

   A mid-sized company plans to consolidate three legacy systems into a single Salesforce org. The company has 5,000 users and expects 2 million Account records. The sales team needs a 360-degree view of customers, while the support team needs access to the same Accounts but only their own Cases. The integration team will sync data from an external ERP using REST APIs. What is the most important architectural consideration for this single-org design?

   • ADesigning the data model with external IDs to avoid duplicate Account records during migration.
   • BStoring all ERP data in custom objects to avoid hitting standard object limits.
   • CConfiguring Organization-Wide Defaults (OWD) to Private for Case and using sharing rules to grant support team access.
   • DUsing a single Profile for all users to simplify administration and ensure consistent access.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A company has a single Salesforce org with 10,000 users and a large custom object that stores 50 million records. Users report slow performance when running reports and list views on this object. The data is rarely updated after creation. The architect needs to improve performance without adding custom code. What should the architect recommend?

   • AEnable Skinny Tables on the custom object to improve report and list view performance.
   • BUse a custom index on all fields of the custom object.
   • CMove the custom object to a separate Salesforce org to reduce data volume.
   • DIncrease the number of records per page in list views to reduce the number of queries.
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   A global company is planning to expand from one Salesforce org to multiple orgs. The company has three business units that operate independently but share a common customer master. The architect must decide on an org strategy. What is the primary driver for choosing a multi-org architecture in this scenario?

   • ATo simplify reporting across the entire company by consolidating data in one place.
   • BTo reduce the total cost of ownership by avoiding per-user licensing fees.
   • CTo provide data isolation between business units that have different regulatory or security requirements.
   • DTo eliminate the need for sharing rules within each business unit.
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A company has three Salesforce orgs: Dev, UAT, and Production. The release management process requires that changes be promoted from Dev to UAT and then to Production. The architect wants to automate the deployment process. What is the most appropriate tool for this?

   • AUse the Metadata API to manually deploy changes to each org.
   • BUse a change set to deploy changes from Dev to UAT and then to Production.
   • CUse a sandbox refresh to copy changes from Dev to UAT and Production.
   • DUse the Salesforce CLI with the 'sfdx force:source:deploy' command for each environment.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A company has two Salesforce orgs: Org A (Sales) and Org B (Service). Sales users in Org A need to view Service Cases from Org B in real-time. The architect wants to avoid data duplication and minimize custom code. What is the most appropriate approach?

   • AUse a custom REST API in Org B that Org A calls on-demand.
   • BUse a nightly batch job to copy Cases from Org B to Org A.
   • CUse Salesforce-to-Salesforce (S2S) to share Cases from Org B to Org A.
   • DUse Salesforce Connect to create an external object in Org A that references Cases in Org B.
   Reveal Solution Discussion Select an answer first