scrumbler interview questions

 1)Settimeout in the promise

let print3 = async(timeout)=>{

    console.log(timeout)

    return new Promise((resolve,reject)=>{

        setTimeout(()=>{

            console.log("3");

            resolve('res');

        }, timeout)

    })

}

print3(10000).then((res)=>{

    console.log(res)

})

2)Clouser 2*8:

def multiply_numbers(x):

    def multiply(y):

        return x * y

    return multiply

# Creating a closure instance for multiplying by 5

multiply_by_5 = multiply_numbers(5)

# Using the closure instance to multiply a number

result = multiply_by_5(7)

print(result)  # Output: 35

3)

In JavaScript, a higher-order function is a function that takes one or more functions as arguments and/or returns a function as its result. Here's an example to demonstrate higher-order functions in JavaScript:

4)multicore process do they use the same port?

No, in Node.js (or any other programming language/framework), you cannot bind multiple processes to the same port. When using a multicore system, each process or worker should listen on a different port.

In the example provided in the previous response, each worker process was set to listen on port 3000. This is possible because each worker process is running as a separate instance, utilizing a different CPU core. The load balancer or network infrastructure in front of your Node.js application can distribute incoming requests across these worker processes using techniques like round-robin or other load balancing algorithms.

By spreading the workload across multiple ports and worker processes, you can achieve parallel processing and take advantage of the multicore system's capabilities. However, it is essential to ensure that the load balancer or proxy in front of your Node.js application is properly configured to distribute the traffic to the available worker processes.

No, in Node.js (or any other programming language/framework), you cannot bind multiple processes to the same port. When using a multicore system, each process or worker should listen on a different port.

In the example provided in the previous response, each worker process was set to listen on port 3000. This is possible because each worker process is running as a separate instance, utilizing a different CPU core. The load balancer or network infrastructure in front of your Node.js application can distribute incoming requests across these worker processes using techniques like round-robin or other load balancing algorithms.

By spreading the workload across multiple ports and worker processes, you can achieve parallel processing and take advantage of the multicore system's capabilities. However, it is essential to ensure that the load balancer or proxy in front of your Node.js application is properly configured to distribute the traffic to the available worker processes.

4)200 -> status code series

200 OK:

• This is the most common status code in the 2xx series. It indicates that the request was successful, and the server has returned the requested resource or performed the requested action.

201 Created:

• This status code indicates that the request has been fulfilled, and a new resource has been created as a result. It is typically used in response to a POST request to indicate the successful creation of a new resource.

202 Accepted:

• This status code indicates that the request has been accepted for processing but has not been completed yet. It is often used for asynchronous operations where the server needs more time to fulfill the request.

204 No Content:

• This status code indicates that the server successfully processed the request but is not returning any content in the response body. It is commonly used for actions that do not require a response body, such as deleting a resource.

These are just a few examples of the 2xx series status codes. Each code within this series carries its own specific meaning, providing information about the success and outcome of the client's request.