Describe an analytics workload on Azure →mediumMultiple ChoiceObjective-mapped

DP-900 Describe an analytics workload on Azure Practice Question

Exhibit

Refer to the exhibit.

```json
{
  "type": "Microsoft.StreamAnalytics/streamingjobs",
  "apiVersion": "2020-03-01",
  "properties": {
    "sku": {
      "name": "StandardV2"
    },
    "inputs": [
      {
        "name": "input",
        "properties": {
          "type": "Stream",
          "datasource": {
            "type": "Microsoft.EventHub/EventHub",
            "properties": {
              "eventHubName": "telemetry-events",
              "consumerGroupName": "$Default"
            }
          }
        }
      }
    ],
    "outputs": [
      {
        "name": "output",
        "properties": {
          "datasource": {
            "type": "Microsoft.Sql/Server/Database",
            "properties": {
              "server": "sqlserver123.database.windows.net",
              "database": "sqldb",
              "table": "SensorData"
            }
          }
        }
      }
    ],
    "transformation": {
      "name": "TransformTelemetry",
      "properties": {
        "streamingUnits": 6,
        "query": "SELECT SensorId, AVG(Temperature) AS AvgTemp INTO output FROM input GROUP BY SensorId, TumblingWindow(minute, 5)"
      }
    }
  }
}
```

Refer to the exhibit. You deploy this Azure Stream Analytics job. The job runs but no data is written to the Azure SQL Database table. What is the most likely cause?

⚠ Common exam trap

Test-takers frequently assume a running job with no errors means data should flow immediately, but they overlook that tumbling windows require the full window duration to elapse before any output is produced.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The TumblingWindow has not yet elapsed

The TumblingWindow function in Azure Stream Analytics processes data in fixed, non-overlapping time intervals. Since the job runs but no data is written, the most likely cause is that the first window has not yet elapsed, meaning no aggregation has been triggered to output results. Stream Analytics only emits results when a tumbling window completes, so data will not appear in the SQL Database until the window duration passes.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The query syntax is invalid
Why it's wrong here
The query uses `TumblingWindow(second, 5)` with a correctly formed `GROUP BY` clause, which is a valid and documented windowing function in the Azure Stream Analytics query language. If the syntax were truly invalid, the job would fail during validation or when attempting to start, not silently produce zero rows. Since the job is running, the query has already been accepted by the Stream Analytics service.
✓
The TumblingWindow has not yet elapsed
Why this is correct
A tumbling window is a fixed-duration, non-overlapping time interval, and Stream Analytics emits aggregate results only after the window's end time is reached. If the job has been running for less than 5 minutes (the window size), the first window has not yet closed, so no aggregated rows are written to the SQL output. This perfectly matches the observed behavior of a started job with zero output.
✗
The Event Hub name is incorrect
Why it's wrong here
If the Event Hub name were incorrect, the Stream Analytics job would fail to establish an input connection and would log an input-not-ready or authentication error at startup; it would not run silently and produce no output. The input alias references the Event Hub correctly, and because the job is actively running, the input connection is valid. Misconfigured input names typically surface as job-start failures, not missing window results.
✗
The SKU does not support SQL output
Why it's wrong here
Azure Stream Analytics supports Azure SQL Database as an output sink across all service tiers, including the StandardV2 SKU referenced in the exhibit. If the SKU did not support SQL output, the job would fail during output validation with an unsupported output type error, before the query could ever run. Since the job is operational, the SKU is not the reason for the empty result set.

Go deeper

DP-900 Describe an analytics workload on Azure Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question