Node2 | MyTaskPanel Consulting

Bienvenido al test sobre Node.js

Para comenzar pulsa sobre el botón de Iniciar.
Dispones de 15 minutos para responder el mayor número posible de respuestas correctas.
Las preguntas tendrán una única respuesta correcta.
Si has terminado el test antes del tiempo establecido, pulsa el botón Finalizar para enviarlo.

Para comenzar el test, completa tus datos y pulsa el botón "Siguiente"

Nombre completo

Use regular expressions directly on the file

Use readline together with streams to read and transform and write the file contents line by line

Use Promises and async/await to offload the task to libuv

Copy the file into a database and perform the operations there

p62

Undefined

John

{'John'}

{}

p17

The forked process shares the event loop with the parent process

The forked process will have its own VM instance.

A new VM instance is created and the two VM instances will be shared between the forked process and the parent process.

The forked process shares the same VM thread with the parent process.

Every Node process gets four threads that it can share between its JavaScript VM and the event loop

JavaScript execution in Node.js is single-threaded, but I/O operations are executed using multiple threads

Every Node process runs in a single thread, and all the I/O work is run in that same thread

The event loop is single-threaded, but a JavaScript VM can use multiple threads

exports, require, module, __filename, __dirname

exports, process, require, module, __filename, __dirname

exports, module, __filename, __dirname

exports, __filename, __dirname

As the application code runs asynchronously within a single thread, the execution will block, accepting no more requests until the operation is completed.

As Node.js is asynchronous, this is handled by a threadpool and the performance will not notably degrade.

As Node.js is asynchronous, this is handled by a libuv and a threadpool. The performance will not notably degrade.

The current thread will block until the executon is completed and the operating system will spawn new threads to handle incoming requests. This can exhaust the number of allowed threads (255) and degrade performance over time.