Exam Integration-Architect Topic 4 Question 54 Discussion

When integrating high-security back-office systems like an Enterprise Billing System (EBS) and a Document Management System (DMS) with Salesforce, the primary concern for an Integration Architect is maintaining the integrity of the organization's existing security perimeter. In an enterprise landscape with over
10 million customers, these systems are typically governed by strict regulatory and compliance standards (such as PCI-DSS or GDPR) that dictate who can view financial records.
The consultant must consider Enterprise security needs for access to these systems rather than simply attempting to synchronize credentials. This involves evaluating an Identity Federation strategy using protocols like SAML 2.0 or OpenID Connect. Instead of maintaining a separate silo of authentication details within Salesforce (which creates a security risk and administrative overhead), Salesforce should act as a Service Provider (SP) that trusts a central Identity Provider (IdP).1234 Furthermore, the "seamle5ss access" requirement implies that once a support agent is authenticated into Salesforce, their identity should be propagated to the EBS and DMS to authorize the specific 6view of a7 customer's bill. This is often achieved through Single Sign-On (SSO) and Token-Based Authentication8.
By prioritizing the enterprise security framewo9rk, the architect ensures that access is auditable, centralized, and compliant with corporate policies, while providing th10e "360-degree" view required by support agents without forcing them to log in to multiple disconnected systems. Migrating such massive systems (Option A) into Salesforce is technically and financially unfeasible for most enterprises due to data volume and specialized processing logic.