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

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 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(a); let a = 10;

A). undefined

B). 10

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 e = 25; function test() { console.log(e); let e = 30; } test();

A). 25

B). 30

C). undefined

D). ReferenceError

In which scope are let variables hoisted?

A). Function scope

B). Block scope

C). Global scope

D). Module scope

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?

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

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