Universal Container (UC) stores 10 million rows of inventory data in a cloud database, As part of creating a connected experience in Salesforce, UC would like to this inventory data to Sales Cloud without a import. UC has asked its data architect to determine if Salesforce Connect is needed. Which three consideration should the data architect make when evaluating the need for Salesforce Connect?
A.
You want real-time access to the latest data, from other systems.
B.
You have a large amount of data and would like to copy subsets of it into Salesforce.
C.
You need to expose data via a virtual private connection.
D.
You have a large amount of data that you don't want to copy into your Salesforce org.
E.
You need to small amounts of external data at any one time.
A.
You want real-time access to the latest data, from other systems.
D.
You have a large amount of data that you don't want to copy into your Salesforce org.
E.
You need to small amounts of external data at any one time.
Explanation:
Salesforce Connect fits best when:
A (Real-time access): You require real-time visibility without data copying.
D (Large data volume, no copying desired): Ideal to avoid storage overhead.
E (Small subsets at a time): Salesforce Connect performs best when accessing smaller, focused datasets in real-time.
Option B describes traditional import scenarios, opposite of Salesforce Connect's design. Option C (VPN exposure) relates to network infrastructure, not specifically Salesforce Connect capabilities. Salesforce Connect excels at external, real-time access without data duplication or large-volume storage impacts.