A newly configured connector authenticates successfully but returns no rows for a table the source team confirms has data. What should be checked first?
Select an answer to reveal the explanation.
Short Explanation
You’ve authenticated, but that doesn’t mean the account can read that table. Check the source-side read grant on that object first, because connectors often return zero rows instead of an error when authorization is missing.
Full Explanation
Authentication proves identity; authorization decides what that identity may read. A connector account that logs in without object-level grants commonly returns an empty result rather than a hard failure, which is exactly the symptom described. The first thing to check is whether the connecting account has read permission on that specific object in the source.
The option about resizing the lakehouse engine is incorrect because engine capacity affects execution speed, never row visibility.
The option about re-exporting source data in a different file format is incorrect because format is irrelevant when the connector is reading the source system directly rather than files.
The option about replacing the connector with a different connector type is incorrect because swapping connectors before diagnosing the cause is guesswork, and the replacement will inherit the same permission gap.
For the exam, when a connection works but returns nothing, look at source-side authorization before touching infrastructure.