DATA-ARCHITECT practice question 14 of 35

Northern trail Outfitters (NTO) runs its entire out of an enterprise data warehouse (EDW), NTD’s sales team starting to use Salesforce after a recent…

Full set: 257 questions
Northern trail Outfitters (NTO) runs its entire out of an enterprise data warehouse (EDW), NTD’s sales team starting to use Salesforce after a recent implementation, but currently lacks data required to advanced and opportunity to the next stage. NTO’s management has research Salesforce Connect and would like to use It to virtualize and report on data from the EDW within Salesforce. NTO will be running thousands of reports per day across 10 to 15 external objects. What should a data architect consider before implementing Salesforce Connect for reporting?
Answer options
A: Maximum number for records returned
B: OData callout limits per day Correct answer
C: Maximum page size for server-driven paging
D: Maximum external objects per org
Correct Answer:
B. OData callout limits per day
Explanation

Salesforce Connect uses OData callouts to retrieve data from external systems. The Salesforce platform enforces governor limits on the number of callouts per user, per hour, and per day to ensure platform stability. With thousands of reports running daily, each potentially triggering multiple callouts, the organization is at high risk of exceeding these daily limits. This would cause reports and other external object access to fail, making it the most critical consideration for a high-volume reporting scenario.

Why Incorrect

A. Maximum number for records returned: While a limit exists (2,000 records per callout), the primary concern with thousands of reports is the total number of callouts, not the size of each one.
C. Maximum page size for server-driven paging: This is a technical detail of data retrieval. The overall callout consumption from numerous report executions is a more immediate and impactful architectural constraint.
D. Maximum external objects per org: The limit is 200 external objects. The planned usage of 10-15 is well within this limit and therefore not a primary concern.

References

1. Salesforce Developer Documentation, "General Limits for Salesforce Connect—All Adapters". This document explicitly lists the "Total OData callouts (per hour)" and "Maximum number of OData callouts (per day)" limits, which are central to the question's scenario.

2. Salesforce Architects, "Salesforce Connect". Under the "When to Use Salesforce Connect" section, it advises considering data access volume, stating, "If you need to access a small amount of external data on an infrequent basis, Salesforce Connect is a good choice." This implies high-volume access is a concern.

3. Salesforce Help, "Salesforce Connect Considerations". This guide notes, "Accessing external objects can be slower than accessing standard and custom objects... High data-access volume from many users can cause you to reach rate limits on your external system."

Scroll to Top