Salesforce-Platform-Integration-Architect Practice Test
Salesforce Spring 25 Release 106 Questions
A company in a heavily regulated industry requires data in legacy systems to be displayed in Salesforce user interfaces (UIs). They are proficient in their cloud-based ETL (extract, transform, load) tools. They expose APIs built on their on-premise middleware to cloud and on-premise applications. Which two findings about their current state will allow copies of legacy data in Salesforce? Choose 2 answers
A.
Only on-premise systems are allowed access to legacy systems
B.
Cloud-based ETL can access Salesforce and supports queues
C.
On-premise middleware provides APIs to legacy systems data
D.
Legacy systems can use queues for on-premise integration
B.
Cloud-based ETL can access Salesforce and supports queues
C.
On-premise middleware provides APIs to legacy systems data
Explanation:
To replicate legacy data into Salesforce, you need both:
B. Cloud-based ETL can access Salesforce and supports queues.
Modern cloud ETL platforms (e.g., AWS Glue) offer native Salesforce connectors that read/write Salesforce objects and can orchestrate jobs in response to queue-based triggers, ensuring reliable delivery and retry semantics.
C. On-premise middleware provides APIs to legacy systems data.
Since the middleware already exposes REST/SOAP endpoints for legacy data, the ETL tool can pull from those APIs, transform the payloads, and load the data into Salesforce custom objects—completing the extract and load steps without building custom adapters.
Answers A and D are constraints on the legacy side (on-prem only or queue-only) but do not by themselves enable ETL-driven replication into Salesforce.