Answer & Solution
let declarations inside a loop are confined to the block scope of the loop.
let inside a loop?
let declarations inside a loop are confined to the block scope of the loop.
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?
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 i = 50; { let i = 55; console.log(i); } console.log(i);
A). 50 50
B). 55 50
C). 50 55
D). ReferenceError
What will be the output of the following code?
let d; console.log(d); d = 15;
A). undefined
B). 15
C). null
D). ReferenceError
What will be the output of the following code?
{ console.log(b); let b = 20; }
A). 20
B). undefined
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
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
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 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
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