M1.3 module quiz
Ten questions. 80% to pass (8 of 10). Open book, unlimited retakes.
Answers are collapsed under each question. Answer first, then check.
Q1
The cron 0 8 * * 1-5 fires:
A. Every weekday at 8:00 AM in the schedule’s IANA timezone
B. The first five days of each month at 8:00 AM local
C. Every day at 8:00 AM, ignoring the day-of-week
D. Five times at 8:00 AM, then it stops firing
Show answer
Correct: A. Day-of-week 1-5 is Monday to Friday, and the schedule’s timezone handles DST automatically. Writing 0 8 1-5 * * instead puts 1-5 in day-of-month and fires on the first five days of every month.
Q2
A schedule has a stop cron and no start cron. The outcome:
A. The schedule is rejected as invalid at save
B. Resources restart automatically at midnight
C. Resources stop and never restart automatically
D. The stop cron is ignored and nothing stops
Show answer
Correct: C. A one-directional schedule is valid and occasionally intended, but far more often an oversight. The 24-hour weekly grid is the surface that makes the gap visible before you save.
Q3
ZopNight cron does NOT support:
A. Ranges such as 1-5 in the day field
B. L for last-day-of-month and # for nth-occurrence
C. Steps such as */15 used in the minute field alone
D. Lists such as 1,3,5 in the day field
Show answer
Correct: B. Also unsupported: the ? placeholder, W, a seconds field and a year field. Take care: the save check lets L, #, ? and W through, so a schedule that uses them saves and then never fires. Complex scenarios use multiple crons in one schedule.
Q4
Where ZopNight shows an existing cron in plain English (on group pages and in the Audit Logs), the text is generated by:
A. A ZopNight-specific parser
B. A large language model
C. The cloud provider’s API
D. The cronstrue library
Show answer
Correct: D. If the plain-English line reads what you intended, the cron is correct; if it disagrees with your intent, the cron is wrong. In the schedule form itself you paint the grid and the crons are written for you.
Q5
The four schedule templates in the schedule form are:
A. Dev, Staging, Production and Demo environments
B. Business Hours, Nights Only, Weekends Off, Dev Hours
C. Daily, Weekly, Monthly and Quarterly cadences
D. Aggressive, Balanced, Conservative and Custom
Show answer
Correct: B. Templates are starting points, not policy: repainting the grid after applying one is the expected path once the workload’s real shape is known. (Peak Hours and Weekend Scale-Down are autoscaler presets, not schedule templates.)
Q6
Exclusive membership on schedule attachment means:
A. A resource follows exactly one scheduling source, so there is no ambiguity about what governs it
B. Only one single schedule is permitted per organisation at any one given moment in time
C. Schedules cannot be shared between different teams
D. A schedule can hold only one resource at a time
Show answer
Correct: A. The constraint exists to make “why did this resource stop?” answerable. Without it, two attachments could apply conflicting crons to the same resource.
Q7
A schedule’s Estimated Savings percentage is computed from:
A. Billed cost measured over the trailing 30 days of usage
B. The provider’s own savings calculator
C. A fixed savings figure set for each resource type
D. The painted grid’s inactive hours divided by 168
Show answer
Correct: D. The percentage is a share of hours, rounded to a whole number: a Business Hours grid (45 running hours) shows 73%. No price goes into it; to get dollars, multiply the attached resources’ always-on compute cost by it yourself.
Q8
Adding resources to a schedule changes its Estimated Savings percentage:
A. Upward
B. Not at all
C. Downward
D. Unpredictably
Show answer
Correct: B. The percentage depends only on the grid, not on the resources. The dollar value you would compute from it rises with the larger cost base, but the share of stopped hours is unchanged.
Q9
A schedule’s timezone is expressed in:
A. A fixed UTC offset
B. The provider region
C. IANA timezone name
D. An ISO country code
Show answer
Correct: C. An IANA name carries DST rules, so 0 8 * * 1-5 in America/New_York stays 8 AM local through both transitions without the cron changing.
Q10
Which failure does the 24-hour weekly grid make visible before you save?
A. A gap where resources are never started
B. Invalid cron syntax in one field
C. A timezone mismatch with the provider
D. Resources attached to two schedules
Show answer
Correct: A. A gap is a visual property, which is exactly what a grid is good at and what reading cron expressions is bad at. Two schedules on one resource cannot happen at all: the second attach is rejected.
What’s next
Back to Build your first schedule.