Core APIs interview questions

1. A.the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
2. B.an abstraction for reading or writing data in chunks rather than all at once
3. C.the promise-based version of the file-system API, for use with async/await
4. D.a fixed-length container for raw binary data allocated outside the V8 heap

Answer + AI explanation with Pro

1. A.Backpressure
2. B.fs.promises
3. C.Stream
4. D.EventEmitter

Answer + AI explanation with Pro

1. A.Stream — a fixed-length container for raw binary data allocated outside the V8 heap
2. B.Stream — an abstraction for reading or writing data in chunks rather than all at once
3. C.Stream — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
4. D.Stream — connects a readable stream to a writable stream, handling backpressure automatically

Answer + AI explanation with Pro

1. A.an abstraction for reading or writing data in chunks rather than all at once
2. B.a fixed-length container for raw binary data allocated outside the V8 heap
3. C.pausing a readable stream when the writable side can't keep up, preventing memory blowup
4. D.the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs

Answer + AI explanation with Pro

1. A.pipe()
2. B.EventEmitter
3. C.Backpressure
4. D.Buffer

Answer + AI explanation with Pro

1. A.Buffer — pausing a readable stream when the writable side can't keep up, preventing memory blowup
2. B.Buffer — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
3. C.Buffer — the promise-based version of the file-system API, for use with async/await
4. D.Buffer — a fixed-length container for raw binary data allocated outside the V8 heap

Answer + AI explanation with Pro

1. A.connects a readable stream to a writable stream, handling backpressure automatically
2. B.pausing a readable stream when the writable side can't keep up, preventing memory blowup
3. C.the promise-based version of the file-system API, for use with async/await
4. D.an abstraction for reading or writing data in chunks rather than all at once

Answer + AI explanation with Pro

1. A.fs.promises
2. B.EventEmitter
3. C.Backpressure
4. D.Buffer

Answer + AI explanation with Pro

1. A.Backpressure — pausing a readable stream when the writable side can't keep up, preventing memory blowup
2. B.Backpressure — the promise-based version of the file-system API, for use with async/await
3. C.Backpressure — connects a readable stream to a writable stream, handling backpressure automatically
4. D.Backpressure — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs

Answer + AI explanation with Pro

1. A.pausing a readable stream when the writable side can't keep up, preventing memory blowup
2. B.an abstraction for reading or writing data in chunks rather than all at once
3. C.the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
4. D.the promise-based version of the file-system API, for use with async/await

Answer + AI explanation with Pro

1. A.pipe()
2. B.Stream
3. C.fs.promises
4. D.EventEmitter

Answer + AI explanation with Pro

1. A.fs.promises — pausing a readable stream when the writable side can't keep up, preventing memory blowup
2. B.fs.promises — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
3. C.fs.promises — connects a readable stream to a writable stream, handling backpressure automatically
4. D.fs.promises — the promise-based version of the file-system API, for use with async/await

Answer + AI explanation with Pro

1. A.pausing a readable stream when the writable side can't keep up, preventing memory blowup
2. B.an abstraction for reading or writing data in chunks rather than all at once
3. C.the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
4. D.connects a readable stream to a writable stream, handling backpressure automatically

Answer + AI explanation with Pro

1. A.pipe()
2. B.fs.promises
3. C.Buffer
4. D.EventEmitter

Answer + AI explanation with Pro

1. A.EventEmitter — connects a readable stream to a writable stream, handling backpressure automatically
2. B.EventEmitter — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
3. C.EventEmitter — the promise-based version of the file-system API, for use with async/await
4. D.EventEmitter — an abstraction for reading or writing data in chunks rather than all at once

Answer + AI explanation with Pro

1. A.the promise-based version of the file-system API, for use with async/await
2. B.the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
3. C.an abstraction for reading or writing data in chunks rather than all at once
4. D.connects a readable stream to a writable stream, handling backpressure automatically

Answer + AI explanation with Pro

1. A.Backpressure
2. B.Stream
3. C.fs.promises
4. D.pipe()

Answer + AI explanation with Pro

1. A.pipe() — the base class providing .on()/.emit() publish-subscribe for Node's event-driven APIs
2. B.pipe() — connects a readable stream to a writable stream, handling backpressure automatically
3. C.pipe() — an abstraction for reading or writing data in chunks rather than all at once
4. D.pipe() — the promise-based version of the file-system API, for use with async/await

Answer + AI explanation with Pro