Before selecting an integration mechanism, the consultant must determine which system is authoritative for each category of business data. This system-of-record decision establishes ownership, governance, synchronization direction, update responsibility, conflict resolution, and the lifecycle of information consumed by Manufacturing Cloud.
For example, account or contact information might originate in Salesforce, while product, order, invoice, or inventory information may be mastered in an ERP or product-management platform. Without explicitly defining ownership, the implementation can produce duplicate records, conflicting updates, inconsistent actual calculations, and unreliable forecasting.
The Agentforce Manufacturing Professional exam guide specifically requires analysis of existing technical architecture with emphasis on data governance, system limitations, and dependencies. It also requires consultants to configure integrations to third-party systems according to the customer's business and technical requirements.
The choice of integration technology comes after the data architecture is understood. A consultant cannot correctly choose between APIs, middleware, batch integration, virtualization, or another pattern until the authoritative source and required flow of each data domain are established.
Current-state process analysis is also important, but the question specifically concerns data in third-party systems, making system-of-record ownership the fundamental consideration.
Study Guide references/topics: Discovery — Data Governance; System of Record; Data Ownership; Third-Party Systems; Integration Dependencies.