When sending data through the HTTP API source connector, how would a data engineer troubleshoot to make sure the payload being sent is formatted properly in real time?

Question

Options

• AUse asynchronous validation query parameter to validate payload matches schema
• BAll data is ingested and query services reporting identify any records that do not pass custom
• CUse synchronous validation query parameter to validate payload matches schema
• DUse query services to validate payloads before sending them via API

• A
  11% (3)
• B
  15% (4)
• C
  70% (19)
• D
  4% (1)

Explanation

Synchronous validation returns pass/fail feedback within the same HTTP response, giving the data engineer immediate, real-time confirmation that the payload matches the expected schema before continuing. This is the only option that closes the feedback loop at the point of transmission.

Why the distractors fail:

• A (asynchronous): Asynchronous validation fires off in the background - the response returns before validation completes, so there's no real-time signal. You're flying blind until you go looking for results.
• B (ingest all, query later): This is a reactive approach - bad records are already inside the system by the time you discover them. It's useful for auditing, not live troubleshooting.
• D (query services before sending): Query services operate on data already at rest in the platform. They can't inspect or validate a payload that hasn't been sent yet, and they don't interact with the API transmission layer.

Memory tip: Sync = Same response. If you need to see the validation result right now, use synchronous - the "S" in both stands for "Same moment." Whenever an exam question mentions "real time" or "immediately," that's a signal to pick synchronous over asynchronous.

No community discussion yet for this question.