Question 90 of 846
Develop data processingmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the timeToLive property defines how long the cluster will be kept alive after a data flow completes, allowing subsequent data flows to reuse the cluster. This is critical because spinning up a new integration runtime cluster for every mapping data flow incurs a 5–10 minute cold start latency; by setting a TTL of 10 minutes, you keep the cluster warm so that consecutive data flows can execute immediately without that delay. On the DP-203 exam, this concept tests your understanding of performance optimization in Azure Synapse, often appearing in scenarios where you must reduce pipeline latency or manage costs. A common trap is confusing TTL with a timeout for inactivity—it is not a maximum execution duration, but rather a reuse window after completion. Remember the memory tip: “TTL = Time to Live, not Time to Limit”—it keeps the cluster alive for reuse, not for running longer jobs.

DP-203 Develop data processing Practice Question

This DP-203 practice question tests your understanding of develop data processing. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Exhibit

Refer to the exhibit.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "type": "Microsoft.Synapse/workspaces/integrationRuntimes",
            "apiVersion": "2021-06-01-preview",
            "name": "[concat(parameters('workspaceName'), '/MyManagedVNetIR')]",
            "properties": {
                "type": "Managed",
                "typeProperties": {
                    "computeProperties": {
                        "location": "AutoResolve",
                        "dataFlowProperties": {
                            "computeType": "General",
                            "coreCount": 8,
                            "timeToLive": 10
                        }
                    }
                }
            }
        }
    ]
}

Refer to the exhibit. You are deploying an Azure Synapse Analytics workspace using an ARM template. The template defines a managed virtual network integration runtime. You need to ensure that the integration runtime can run mapping data flows with a time-to-live (TTL) of 10 minutes. What is the purpose of the 'timeToLive' property in this configuration?

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "type": "Microsoft.Synapse/workspaces/integrationRuntimes",
            "apiVersion": "2021-06-01-preview",
            "name": "[concat(parameters('workspaceName'), '/MyManagedVNetIR')]",
            "properties": {
                "type": "Managed",
                "typeProperties": {
                    "computeProperties": {
                        "location": "AutoResolve",
                        "dataFlowProperties": {
                            "computeType": "General",
                            "coreCount": 8,
                            "timeToLive": 10
                        }
                    }
                }
            }
        }
    ]
}

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

It defines how long the cluster will be kept alive after a data flow completes, allowing subsequent data flows to reuse the cluster.

The 'timeToLive' property in an Azure Synapse Analytics managed virtual network integration runtime controls how long the cluster remains alive after a mapping data flow completes. By setting a TTL of 10 minutes, subsequent data flows can reuse the same warm cluster, avoiding the 5–10 minute cold start time for new clusters. This optimizes performance and reduces latency for consecutive data flow executions.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • It defines how long the cluster will be kept alive after a data flow completes, allowing subsequent data flows to reuse the cluster.

    Why this is correct

    TTL keeps the cluster warm for reuse, reducing startup time.

    Related concept

    Read the scenario before looking for a memorised answer.

  • It sets the timeout for the integration runtime to connect to the data sources.

    Why it's wrong here

    Connection timeout is a separate setting.

  • It specifies the maximum duration a data flow activity can run before timing out.

    Why it's wrong here

    Activity timeout is set at the activity level, not by timeToLive.

  • It determines the maximum number of concurrent data flows that can run on the cluster.

    Why it's wrong here

    Concurrency is controlled by the core count and other settings.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse 'timeToLive' with activity timeout or concurrency limits, because all three involve time or capacity constraints, but TTL specifically governs cluster reuse after a data flow completes, not execution duration or parallelism.

Detailed technical explanation

How to think about this question

Under the hood, the TTL property leverages Azure's Spark cluster pooling mechanism. When a data flow completes, the cluster is not immediately deallocated; instead, it enters an idle state for the TTL duration. During this window, new data flows are routed to the existing cluster, bypassing the provisioning overhead. In real-world scenarios, setting a TTL of 10 minutes is ideal for bursty workloads where multiple data flows run in quick succession, but a longer TTL (e.g., 60 minutes) can waste compute resources if no subsequent flows arrive.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related DP-203 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DP-203 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DP-203 question test?

Develop data processing — This question tests Develop data processing — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: It defines how long the cluster will be kept alive after a data flow completes, allowing subsequent data flows to reuse the cluster. — The 'timeToLive' property in an Azure Synapse Analytics managed virtual network integration runtime controls how long the cluster remains alive after a mapping data flow completes. By setting a TTL of 10 minutes, subsequent data flows can reuse the same warm cluster, avoiding the 5–10 minute cold start time for new clusters. This optimizes performance and reduces latency for consecutive data flow executions.

What should I do if I get this DP-203 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DP-203 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-203 exam.