Why promises are used in Javascript - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do we use promises in JavaScript?

Which of the following best explains why promises are used in JavaScript?

A To handle asynchronous operations and avoid callback hell by chaining actions.

B To make JavaScript code run faster by using multiple CPU cores.

C To store data permanently in the browser's memory.

D To convert synchronous code into asynchronous code automatically.

💡 Hint

Think about how JavaScript handles tasks that take time, like loading data from the internet.

Promises help manage asynchronous tasks by allowing code to run after a task finishes, avoiding deeply nested callbacks.

❓ Predict Output

intermediate

Output of promise chaining

What will be the output of the following JavaScript code?

Javascript

Promise.resolve(5)
  .then(x => x * 2)
  .then(x => x + 3)
  .then(console.log);

A 10

B undefined

C 13

D Error

💡 Hint

Follow the value through each then step.

The promise starts with 5, then multiplies by 2 (10), then adds 3 (13), and finally logs 13.

❓ Predict Output

advanced

Promise error handling output

What will this code print to the console?

Javascript

Promise.reject('fail')
  .catch(err => 'recovered')
  .then(console.log);

A fail

B Error

C undefined

D recovered

💡 Hint

Look at how the catch changes the flow.

The promise rejects with 'fail', but catch handles it and returns 'recovered', which is logged.

🧠 Conceptual

advanced

Why promises improve code readability

Which statement best describes how promises improve JavaScript code readability?

A They automatically parallelize all asynchronous tasks for faster execution.

B They allow asynchronous code to be written in a linear, easy-to-follow style using chaining.

C They replace all functions with classes for better structure.

D They force all asynchronous code to run synchronously.

💡 Hint

Think about how promises let you write steps one after another.

Promises let you chain asynchronous steps in a clear, linear way, avoiding nested callbacks.

❓ Predict Output

expert

Promise.all behavior with mixed promises

What will be the output of this code?

Javascript

Promise.all([
  Promise.resolve(1),
  Promise.reject('error'),
  Promise.resolve(3)
])
.then(console.log)
.catch(console.log);

A error

B [1, 3]

C [1, 'error', 3]

D undefined

💡 Hint

Remember how Promise.all behaves when one promise rejects.

Promise.all rejects immediately if any promise rejects, so the catch logs 'error'.

Practice

1. Why are promises used in JavaScript?
Promise helps with:

easy

A. Storing data permanently

B. Making the program run slower

C. Writing code without any functions

D. Handling tasks that take time without stopping the program

Solution

1. Step 1: Understand what promises do

   Promises allow JavaScript to handle tasks like loading data without freezing the program.

2. Step 2: Identify the correct purpose

   Promises help manage asynchronous tasks so the program keeps running smoothly.

3. Final Answer:

   Handling tasks that take time without stopping the program -> Option D

4. Quick Check:

   Promises = handle async tasks without blocking [OK]

Hint: Promises handle slow tasks without freezing code [OK]

Common Mistakes:

• Thinking promises slow down the program
• Confusing promises with data storage
• Believing promises remove the need for functions

2. Which of the following is the correct way to create a promise in JavaScript?

easy

A. let p = new Promise((resolve, reject) => { /* code */ });

B. let p = Promise.create(() => { /* code */ });

C. let p = promise(() => { /* code */ });

D. let p = new promise { /* code */ };

Solution

1. Step 1: Recall correct Promise syntax

   Promises are created with new Promise and a function with resolve and reject parameters.

2. Step 2: Check each option

   Only let p = new Promise((resolve, reject) => { /* code */ }); uses the correct syntax with new Promise and arrow function.

3. Final Answer:

   let p = new Promise((resolve, reject) => { /* code */ }); -> Option A

4. Quick Check:

   Correct Promise syntax = new Promise(...) [OK]

Hint: Use 'new Promise' with resolve and reject functions [OK]

Common Mistakes:

• Using lowercase 'promise' instead of 'Promise'
• Trying to call Promise.create which doesn't exist
• Missing parentheses or arrow function syntax

3. What will be the output of this code?

const p = new Promise((resolve) => {
  setTimeout(() => resolve('Done'), 100);
});
p.then(result => console.log(result));
console.log('Start');

medium

A. StartDone

B. DoneStart

C. DoneDone

D. StartStart

Solution

1. Step 1: Understand asynchronous behavior

   The setTimeout delays the resolve call by 100ms, so console.log('Start') runs first.

2. Step 2: Trace the output order

   First, 'Start' prints immediately, then after 100ms, 'Done' prints from the promise.

3. Final Answer:

   Start
   Done -> Option A

4. Quick Check:

   Async delay means 'Start' before 'Done' [OK]

Hint: setTimeout delays promise resolution, so logs appear after immediate code [OK]

Common Mistakes:

• Assuming promise resolves immediately
• Thinking 'Done' prints before 'Start'
• Ignoring asynchronous nature of setTimeout

4. Find the error in this promise code:

const p = new Promise((resolve, reject) => {
  resolve('Success');
  reject('Error');
});
p.then(result => console.log(result))
 .catch(error => console.log(error));

medium

A. Promise must call reject first

B. Calling reject after resolve has no effect

C. Missing semicolon after resolve

D. Then and catch cannot be chained

Solution

1. Step 1: Understand promise state changes

   Once a promise is resolved or rejected, its state is final and cannot change.

2. Step 2: Analyze the code flow

   The promise calls resolve('Success') first, so the later reject('Error') is ignored.

3. Final Answer:

   Calling reject after resolve has no effect -> Option B

4. Quick Check:

   Promise settles once; later calls ignored [OK]

Hint: Promise settles once; later resolve/reject calls ignored [OK]

Common Mistakes:

• Thinking reject overrides resolve if called later
• Believing then and catch can't be chained
• Confusing semicolon placement with logic errors

5. You want to fetch user data and then fetch posts for that user. Which approach best uses promises to handle this sequence?

hard

A. Use setTimeout to delay fetchPosts() after fetchUser()

B. Call fetchUser() and fetchPosts() separately without waiting

C. Call fetchUser(), then inside its .then(), call fetchPosts() and return that promise

D. Call fetchPosts() first, then fetchUser() inside its .then()

Solution

1. Step 1: Understand promise chaining for dependent tasks

   When one task depends on another, use .then() to wait for the first before starting the second.

2. Step 2: Identify correct chaining

   Call fetchUser(), then inside its .then(), call fetchPosts() and return that promise correctly calls fetchUser(), then in its .then(), calls fetchPosts() and returns its promise to chain properly.

3. Final Answer:

   Call fetchUser(), then inside its .then(), call fetchPosts() and return that promise -> Option C

4. Quick Check:

   Promise chaining = dependent tasks in sequence [OK]

Hint: Chain promises with then() for dependent async tasks [OK]

Common Mistakes:

• Running dependent tasks in parallel without waiting
• Using setTimeout instead of promise chaining
• Calling tasks in wrong order