Q
How can you avoid variable hoisting issues with let?

Answer & Solution

Answer: Option C
Solution:
Declaring let variables at the top of their block scope avoids TDZ issues and hoisting-related errors.
Related Questions on Average

What will be the output of the following code?

let i = 50; { let i = 55; console.log(i); } console.log(i);

A). 50 50

B). 55 50

C). 50 55

D). ReferenceError

Which keyword should be used to declare variables that do not get re-assigned?

A). let

B). const

C). var

D). function

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?

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 f = 10; if (true) { console.log(f); let f = 20; }

A). 10

B). 20

C). undefined

D). ReferenceError

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 scope of a variable declared with let inside a loop?

A). Global scope

B). Function scope

C). Block scope

D). Module scope

What will be the output of the following code?

console.log(a); let a = 10;

A). undefined

B). 10

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

Where should let variables be declared to avoid TDZ issues?

A). At the top of the global scope

B). At the bottom of their block scope

C). At the top of their block scope

D). Anywhere in the code