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 h = 40; { console.log(h); h = 45; } console.log(h);

A). 40 45

B). 45 45

C). undefined undefined

D). ReferenceError 45

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

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?

let f = 10; if (true) { console.log(f); let f = 20; }

A). 10

B). 20

C). undefined

D). ReferenceError

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 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

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

Which statement about let and const is correct?

A). Both are block scoped, but only let can be re-assigned

B). Both are block scoped, but only const can be re-assigned

C). Only const is block scoped

D). Both are not block scoped

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?

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

A). 50 50

B). 55 50

C). 50 55

D). ReferenceError