Salesforce App Builder Practice Exam

Which use case is NOT appropriate for Lightning Connect?

1. Integrate external data without writing custom code.

2. External data is changing frequently.

3. Set up workflows and triggers for external data.

4. Real-time access to a small fraction of external data.

The correct answer is: Set up workflows and triggers for external data.

The use case involving setting up workflows and triggers for external data is not appropriate for Lightning Connect. Lightning Connect is designed to provide a way to access and display external data sources in Salesforce without the need for complex coding. It effectively allows users to view and interact with that data in real time, but it does not natively support creating workflows or triggers based on changes to external data. When it comes to other options, integrating external data without writing custom code is a primary advantage of Lightning Connect; it streamlines the integration process and allows users to focus on configuration rather than programming. In scenarios where external data is changing frequently, Lightning Connect performs well since it can pull in real-time data updates from external sources. Additionally, the ability to provide real-time access to a small fraction of external data can be effectively achieved using Lightning Connect, as it makes selected external information available as if it were native Salesforce data without needing to replicate it within Salesforce itself. Thus, the main distinction for why setting up workflows and triggers does not align with Lightning Connect's capabilities is that it lacks the ability to initiate automated actions based on external data changes within Salesforce.