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

Questions 31–33

1. 31foundation · easy

   How do API request limits differ between a single org and a multi-org environment?

   • AMulti-org environments have unlimited API calls
   • BSingle orgs have no API limits
   • CIn a multi-org environment, API limits are combined into a single pool
   • DIn a single org, the API limit is shared across all integrations
   Reveal Solution Discussion Select an answer first
2. 32foundation · easy

   What is a primary architectural implication of using point-to-point integration between multiple Salesforce orgs?

   • AIt centralizes error handling
   • BIt reduces the number of connections needed
   • CIt simplifies maintenance and monitoring
   • DIt creates a direct dependency between the connected orgs
   Reveal Solution Discussion Select an answer first
3. 33application · medium

   A company has a single Salesforce org with a custom object 'Contract__c'. The OWD for Contract__c is Public Read Only. The company wants to allow only the 'Legal' role to edit Contracts, while other roles can only view them. What should the architect configure?

   • AKeep OWD as Public Read Only and create a permission set that grants edit access to the Legal role.
   • BUse a manual sharing button on the Contract record to allow Legal to edit.
   • CSet the OWD to Private and use a sharing rule to grant the Legal role edit access.
   • DUse a criteria-based sharing rule to share Contracts where the 'Legal__c' field equals the user.
   Reveal Solution Discussion Select an answer first