Answer & Solution
let creates a new i within the block, logging 55, while the outer i remains 50.
let i = 50; { let i = 55; console.log(i); } console.log(i);
let creates a new i within the block, logging 55, while the outer i remains 50.
How can you avoid variable hoisting issues with let?
A). Declare variables at the bottom of the code
B). Use var instead
C). Declare variables at the top of their scope
D). Do not declare variables
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 d; console.log(d); d = 15;
A). undefined
B). 15
C). null
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?
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?
let e = 25; function test() { console.log(e); let e = 30; } test();
A). 25
B). 30
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
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?
{ console.log(b); let b = 20; }
A). 20
B). undefined
C). null
D). ReferenceError