JavaScript Explicit Resource Management — Quiz

Question 1 of 19

What is the primary purpose of Explicit Resource Management?

Answer options A Deterministic cleanup tied to scope completion B Forcing garbage collection C Weakening object references D Changing module linking

The feature gives resource cleanup a deterministic scope-based lifetime.

Question 2 of 19

Which well-known Symbol identifies synchronous disposal?

Answer options A Symbol.dispose B Symbol.asyncDispose C Symbol.iterator D Symbol.toPrimitive

Symbol.dispose is the synchronous disposal protocol hook.

Question 3 of 19

Which protocol is used for asynchronous disposal?

Answer options A Symbol.asyncDispose B Symbol.dispose C Symbol.asyncIterator D Symbol.match

Symbol.asyncDispose identifies asynchronous cleanup that returns a Promise.

Question 4 of 19

What does a using declaration do?

Answer options A Registers a resource for disposal when its containing scope completes B Immediately disposes the resource C Makes the resource weak D Clones the resource

using associates the resource with scope-completion disposal.

Question 5 of 19

What is special about await using?

Answer options A Its asynchronous disposal is awaited B It only works with numbers C It disables exceptions D It forces synchronous cleanup

await using is designed for resources whose cleanup is asynchronous.

Question 6 of 19

In what order are resources in a disposal stack released?

Answer options A Reverse registration order B Registration order C Random order D Sorted by name

Disposable resource stacks are LIFO.

Question 7 of 19

What does DisposableStack.use(value) do?

Answer options A Registers a disposable value on the stack B Immediately disposes value C Converts value to a Promise D Creates a WeakRef

use adds a disposable resource to the stack.

Question 8 of 19

What does DisposableStack.adopt(value, onDispose) provide?

Answer options A A custom cleanup callback associated with a value B Automatic garbage collection C A new Realm D A Promise reaction

adopt lets a stack own a value with caller-supplied cleanup logic.

Question 9 of 19

What does DisposableStack.defer(onDispose) register?

Answer options A Cleanup callback without requiring a resource value B An iterator C A finalizer tied to GC D A module export

defer records a cleanup callback for stack disposal.

Question 10 of 19

What is the purpose of DisposableStack.move()?

Answer options A Transfer pending ownership to a new stack B Copy every resource C Dispose both stacks D Disable cleanup

move transfers the pending resource stack and marks the original disposed.

Question 11 of 19

What is AsyncDisposableStack for?

Answer options A Aggregating asynchronously disposable resources B Weakly storing objects C Parsing modules D Scheduling DOM tasks

AsyncDisposableStack manages resources whose cleanup may require awaiting.

Question 12 of 19

Which statement is correct about garbage collection and disposal?

Answer options A Explicit disposal should not depend on GC timing B Disposal waits for GC C GC always calls Symbol.dispose D WeakRef is required for disposal

Required resource cleanup should be explicit and deterministic.

Question 13 of 19

Does using replace try/finally for every purpose?

Answer options A No; try/finally remains general-purpose control flow B Yes; try/finally is obsolete C Only in browsers D Only for async functions

using specializes resource cleanup; try/finally remains a general control-flow construct.

Question 14 of 19

Can disposal affect the final program completion?

Answer options A Yes; disposal errors can propagate B No; disposal errors are discarded C Only syntax errors can propagate D Only GC errors propagate

Disposal is part of scope completion and its errors participate in completion propagation.

Question 15 of 19

Why feature-detect modern resource-management APIs?

Answer options A Deployed runtimes may not yet support every current feature B The APIs are optional in the specification C Detection changes the language semantics D It makes GC deterministic

Runtime support can lag the current ECMAScript specification.

Question 16 of 19

Where should cleanup responsibility usually live?

Answer options A With the resource abstraction that owns the cleanup operation B In an unrelated global singleton C Only in a finalizer D Only in the caller UI

Keeping cleanup with the resource abstraction makes ownership and lifetime clearer.

Question 17 of 19

Why does disposal sometimes create a SuppressedError?

Answer options A To preserve both an existing abrupt completion and a new disposal failure B To force cleanup to succeed C To make errors enumerable D To replace AggregateError

SuppressedError preserves the earlier completion while exposing the later disposal failure.

Question 18 of 19

Which relationship is correct?

Answer options A error is the earlier failure; suppressed is the later cleanup failure B error is the later cleanup failure; suppressed is the earlier completion C both properties contain arrays D both properties always contain the same Error

The disposal algorithm puts the newly thrown cleanup error in error and the previously active abrupt completion in suppressed.

Question 19 of 19

How does SuppressedError differ from AggregateError?

Answer options A SuppressedError has error and suppressed; AggregateError has an errors collection B They have identical structure C AggregateError only represents cleanup D SuppressedError contains an errors array

They represent different error relationships.

JavaScript Explicit Resource Management — Quiz