Frontend interview answer
The interactive answer choices load in your browser.
This JavaScript interview question tests whether you can explain JavaScript output: nested microtasks before a zero-delay timer, connect it to production trade-offs, and handle common follow-up questions.
Use this JavaScript interview question to rehearse a quick answer, common mistake, follow-up, and production pitfall.
Result and execution phases
The output is A, E, C, D, then B. The browser starts by running the script as the current task. console.log('A') runs immediately, setTimeout makes its callback eligible for a later task, and Promise.then queues a microtask. The final synchronous statement logs E. Only after the script's call stack is empty does the browser begin the microtask checkpoint, so the Promise callback logs C before the timer can run.
Phase | What happens | Output added |
|---|---|---|
Current script task | Synchronous statements run; the timer and Promise callback are scheduled. | A, E |
Microtask checkpoint | The Promise callback runs and queues another microtask with queueMicrotask. | C, D |
Next task | The zero-delay timer callback can finally run. | B |
Why the nested microtask still wins
While the Promise callback is running, queueMicrotask appends the callback that logs D to the same microtask queue. A microtask checkpoint continues until that queue is empty, including microtasks added by other microtasks. Therefore D runs before the browser selects the timer task that logs B.
A common mistake is to read setTimeout(..., 0) as "run immediately" or to assume scheduling order decides everything. A zero delay only means the timer does not request an additional wait; it does not bypass the current task or pending microtasks. The same rule also explains why a chain that continually queues microtasks can delay timers and rendering.
A
E
C
D
B
Use this as one explanation rep, then continue with the JavaScript interview questions cluster or a guided prep path.