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

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

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

In which scope are let variables hoisted?

A). Function scope

B). Block scope

C). Global scope

D). Module scope

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

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

A). 40 45

B). 45 45

C). undefined undefined

D). ReferenceError 45

What will be the output of the following code?

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

A). undefined

B). 10

C). null

D). ReferenceError