Configure and manage automation of tasks →mediumMultiple ChoiceObjective-mapped

DP-300 Configure and manage automation of tasks Practice 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"
}
```

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?

⚠ Common exam trap

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.

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.

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.

Visual reference

Go deeper

DP-300 Configure and manage automation of tasks Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question