Question 224 of 953
Configure and manage automation of tasksmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is a conflict between the interval and frequency properties. In Azure Elastic Jobs, when you define a frequency like 'Weekly', the interval property—which specifies a duration such as 'PT1H' for hourly runs—becomes incompatible because the schedule is governed by the recurrence pattern, not a repeating time span. This is a common trap on the DP-300 exam, where candidates overlook that including both properties creates a scheduling conflict that prevents the job from executing as intended. The exam tests your understanding of how elastic job schedule conflict resolution works, specifically that interval should be removed when frequency is set to a non-daily recurrence like weekly. To remember: think of frequency as the "what day" and interval as the "how often within that day"—they cannot coexist for weekly schedules. A simple memory tip: "Frequency sets the day, interval sets the delay; keep one to make the job play."

DP-300 Configure and manage automation of tasks Practice Question

This DP-300 practice question tests your understanding of configure and manage automation of tasks. 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.

```
{
    "properties": {
        "startTime": "2024-05-01T00:00:00Z",
        "interval": "PT1H",
        "frequency": "Week",
        "daysOfWeek": [ "Sunday" ],
        "timeZone": "UTC",
        "retentionPolicy": {
            "days": 30
        }
    },
    "type": "Microsoft.Sql/servers/elasticPools/elasticJobAgents/jobs/executions"
}
```

Refer to the exhibit. You are reviewing the JSON configuration for an elastic job. The job is expected to run every week on Sunday at midnight UTC. However, the job is not executing as scheduled. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.

```
{
    "properties": {
        "startTime": "2024-05-01T00:00:00Z",
        "interval": "PT1H",
        "frequency": "Week",
        "daysOfWeek": [ "Sunday" ],
        "timeZone": "UTC",
        "retentionPolicy": {
            "days": 30
        }
    },
    "type": "Microsoft.Sql/servers/elasticPools/elasticJobAgents/jobs/executions"
}
```

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 interval and frequency properties are conflicting; interval should be removed for weekly frequency.

The job configuration includes both an 'interval' property (e.g., 'PT1H' for every hour) and a 'frequency' property set to 'Weekly'. In Azure Elastic Jobs, when 'frequency' is specified, the 'interval' property is ignored or causes a conflict because the schedule is defined by the cron-like recurrence pattern. Removing the 'interval' property resolves the conflict and allows the weekly schedule to execute correctly.

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.

  • The retention policy is set too low, causing the job to be pruned before execution.

    Why it's wrong here

    Retention policy affects execution history, not scheduling.

  • The startTime is in the past; the job should have a future start time.

    Why it's wrong here

    Jobs can start in the past; the schedule will run at the next occurrence.

  • The job definition is missing the 'scheduleType' property.

    Why it's wrong here

    Schedule type is not required; the structure is valid.

  • The interval and frequency properties are conflicting; interval should be removed for weekly frequency.

    Why this is correct

    For weekly frequency, interval is not used; it causes ambiguity.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Microsoft often tests the misconception that both 'interval' and 'frequency' must always be specified together, when in fact for weekly or monthly frequencies, 'interval' is not applicable and its presence causes a scheduling conflict.

Detailed technical explanation

How to think about this question

Azure Elastic Jobs use a recurrence-based scheduling model where 'frequency' (e.g., 'Minute', 'Hour', 'Day', 'Week', 'Month') defines the unit of recurrence, and 'interval' defines how many units between runs. When 'frequency' is set to 'Week', the 'interval' property is not used; instead, the schedule relies on 'startTime' and optional 'weekDays' or 'monthlyOccurrence' properties. Including 'interval' with a weekly frequency creates an invalid configuration that the job scheduler cannot parse, causing the job to never execute.

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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

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-300 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-300 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-300 question test?

Configure and manage automation of tasks — This question tests Configure and manage automation of tasks — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The interval and frequency properties are conflicting; interval should be removed for weekly frequency. — The job configuration includes both an 'interval' property (e.g., 'PT1H' for every hour) and a 'frequency' property set to 'Weekly'. In Azure Elastic Jobs, when 'frequency' is specified, the 'interval' property is ignored or causes a conflict because the schedule is defined by the cron-like recurrence pattern. Removing the 'interval' property resolves the conflict and allows the weekly schedule to execute correctly.

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

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

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 30, 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-300 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-300 exam.