How can you avoid variable hoisting issues with let?

What will be the output of the following code?

let e = 25; function test() { console.log(e); let e = 30; } test();

A). 25

B). 30

C). undefined

D). ReferenceError

What will be the output of the following code?

let d; console.log(d); d = 15;

A). undefined

B). 15

C). null

D). ReferenceError

Which of the following is true about let declarations?

A). They are hoisted and initialized at the top of their scope

B). They are hoisted but not initialized

C). They are not hoisted at all

D). They are function scoped

What will be the output of the following code?

let c = 5; { let c = 10; console.log(c); }

A). 5

B). 10

C). ReferenceError

D). undefined

What happens when you try to re-declare a let variable in the same scope?

A). It reassigns the value

B). It throws a SyntaxError

C). It re-declares the variable

D). It throws a TypeError

What is the scope of a variable declared with let inside a loop?

A). Global scope

B). Function scope

C). Block scope

D). Module scope

What is the advantage of using let over var?

A). let allows for function scoping

B). let does not get hoisted

C). let avoids issues related to the temporal dead zone

D). let is globally scoped

What is the 'temporal dead zone'?

A). The period during which a variable is declared but not yet initialized

B). The time when the variable is accessible throughout the program

C). The period after variable initialization

D). None of the above

What will be the output of the following code?

{ console.log(b); let b = 20; }

A). 20

B). undefined

C). null

D). ReferenceError

What will be the output of the following code?

for (let i = 0; i < 3; i++) { setTimeout(() => console.log(i), 0); }

A). 0 0 0

B). 3 3 3

C). 0 1 2

D). ReferenceError