IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 22 of 30

Universal Containers (UC) operates in Asia, Europe and North America regions. There is one Salesforce org for each region. UC is implementing…

Full set: 248 questions
Universal Containers (UC) operates in Asia, Europe and North America regions. There is one Salesforce org for each region. UC is implementing Customer 360 in Salesforce and has procured External Identity and Customer Community licenses in all orgs. Customers of UC use Community to track orders and create inquiries. Customers also tend to move across regions frequently. What should an identity architect recommend to optimize license usage and reduce maintenance overhead?
Answer options
A: Merge three orgs into one instance of Salesforce. This will no longer require maintaining three separate copies of the same customer. Correct answer
B: Delete contact/ account records and deactivate user if user moves from a specific region; Sync will no longer be required.
C: Contacts are required since Community access needs to be enabled. Maintenance is a necessary overhead that must be handled via data integration.
D: Enable Contactless User in all orgs and downgrade users from Experience Cloud license to External Identity license once users have moved out of that region.
Correct Answer:
A. Merge three orgs into one instance of Salesforce. This will no longer require maintaining three separate copies of the same customer.
Explanation

The most effective architectural solution is to merge the three regional Salesforce orgs into a single global instance. This approach directly addresses the root cause of the issues. By creating a single source of truth for each customer, it eliminates the need for duplicate contact and user records. This fundamentally solves both key requirements:
1. Optimize License Usage: Each customer would have only one user record, consuming a single license, regardless of their location.
2. Reduce Maintenance Overhead: It removes the immense complexity and cost of building and maintaining a data synchronization and identity reconciliation process across three separate systems. This strategy aligns perfectly with the stated goal of implementing "Customer 360," which is predicated on having a unified view of the customer.

Why Incorrect

B: Deleting customer account and contact records would cause a catastrophic loss of historical data, such as past orders and service inquiries, violating data integrity principles. C: This option is a passive acceptance of the problem, not a solution. It correctly identifies a constraint but fails to provide a recommendation to optimize or reduce the resulting overhead. D: While downgrading licenses is a valid tactic for cost optimization, it does not reduce the maintenance overhead of managing a fragmented customer identity across three orgs. It may even increase complexity.

References

1. Salesforce Architects, "The Architect's Guide to Multi-Org Strategy" (Whitepaper), 2021: This guide explicitly lists "No single, 360-degree view of the customer" and "Complex to manage and maintain" as primary disadvantages of a multi-org strategy. Conversely, it cites "Single source of truth for data" and "Easier to manage and maintain" as key advantages of a single-org strategy, directly supporting the recommendation to merge orgs to solve the stated problems. (Refer to sections on "Single-Org Strategy" and "Multi-Org Strategy").

2. Salesforce Help, "Experience Cloud User Licenses": This documentation clarifies that Customer Community licenses are required for users who need access to CRM objects like Orders and are tied to a contact record. This highlights why simply managing licenses (as in option D) doesn't solve the underlying data fragmentation and maintenance problem, as the contact records and their associated data remain siloed in each org.

3. DAMA International, "DAMA-DMBOK: Data Management Body of Knowledge (2nd Edition)": Chapter 3, "Data Architecture," emphasizes the principle of establishing a single source of truth or system of record to reduce data redundancy, improve data quality, and lower maintenance costs. The multi-org scenario described in the question directly contradicts this core data management principle, making consolidation (Option A) the architecturally correct recommendation.

Scroll to Top