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 keyword should be used to declare variables that do not get re-assigned?

A). let

B). const

C). var

D). function

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

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

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?

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 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 difference between let and var in terms of scope?

A). let is function scoped, var is block scoped

B). let is block scoped, var is function scoped

C). Both are function scoped

D). Both are block scoped

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(b); let b = 20; }

A). 20

B). undefined

C). null

D). ReferenceError