Performance monitoring basics in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Understanding CPU usage output from a monitoring tool

You run a command to check CPU usage on a server and get this output:

CPU Usage: 85%

What does this output mean?

A The CPU is idle 85% of the time

B The CPU temperature is 85 degrees

C The CPU is busy 85% of the time

D The CPU usage is below 15%

💡 Hint

CPU usage shows how busy the processor is, not temperature or idle time.

CPU usage percentage tells how much time the CPU spends doing work. 85% means it is busy most of the time.

🧠 Conceptual

intermediate

Purpose of monitoring memory usage in applications

Why is it important to monitor memory usage in a running application?

A To check disk space availability

B To see how fast the CPU is running

C To measure network speed

D To check if the application is using too much memory and might crash

💡 Hint

Memory issues can cause crashes or slowdowns.

Monitoring memory helps detect leaks or excessive use that can cause crashes or poor performance.

🔀 Workflow

advanced

Steps to set up basic performance monitoring on a Linux server

Which sequence correctly describes the steps to set up basic performance monitoring using common Linux tools?

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 4,1,2,3

💡 Hint

Think about installing first, then running, analyzing, and alerting last.

You first install tools, then run them to collect data, analyze that data, and finally set alerts.

❓ Troubleshoot

advanced

Identifying cause of high disk I/O in monitoring logs

Your monitoring logs show very high disk I/O on a server. Which of these is the most likely cause?

A A process is reading and writing large files frequently

B The CPU is overheating

C The network connection is slow

D The server has low memory usage

💡 Hint

Disk I/O relates to reading and writing data on disk.

High disk I/O means a process is doing many read/write operations on the disk.

✅ Best Practice

expert

Choosing the best metric to monitor for web server responsiveness

Which metric is best to monitor to understand if a web server is responding quickly to user requests?

A Average response time per request

B CPU temperature

C Disk space usage

D Number of open network ports

💡 Hint

Think about what shows how fast the server replies to users.

Average response time directly measures how quickly the server handles requests.

Practice

1. What is the main purpose of performance monitoring in an Express app?

easy

A. To measure how fast the app responds to requests

B. To add new features to the app

C. To change the app's user interface

D. To store user data securely

Solution

1. Step 1: Understand performance monitoring

   Performance monitoring tracks how quickly the app handles requests.

2. Step 2: Identify the main goal

   The goal is to find slow parts and improve speed, not to add features or change UI.

3. Final Answer:

   To measure how fast the app responds to requests -> Option A

4. Quick Check:

   Performance monitoring = measure response speed [OK]

Hint: Performance monitoring = measuring app speed [OK]

Common Mistakes:

• Confusing performance monitoring with adding features
• Thinking it changes the user interface
• Assuming it stores user data

2. Which Express middleware code snippet correctly measures request duration?

easy

A. app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); });

B. app.use((req, res, next) => { const start = Date.now(); next(); console.log(Date.now() - start); });

C. app.use((req, res) => { console.log('Request received'); });

D. app.use((req, res, next) => { console.log('Start'); next(); console.log('End'); });

Solution

1. Step 1: Check middleware timing logic

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); }); starts timer, waits for response finish event, then logs duration correctly.

2. Step 2: Compare other options

   app.use((req, res, next) => { const start = Date.now(); next(); console.log(Date.now() - start); }); logs too early before response ends. Another option lacks next() call. The remaining option logs 'Start' and 'End' immediately, not duration.

3. Final Answer:

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { console.log(Date.now() - start); }); next(); }); -> Option A

4. Quick Check:

   Use 'res.on("finish")' to measure full request time [OK]

Hint: Use 'res.on("finish")' event to log after response ends [OK]

Common Mistakes:

• Logging time before response finishes
• Forgetting to call next() in middleware
• Not using response events to measure duration

3. Given this middleware, what will be logged when a request takes 150ms?

app.use((req, res, next) => {
  const start = Date.now();
  res.on('finish', () => {
    console.log(`Response time: ${Date.now() - start}ms`);
  });
  next();
});

medium

A. No output logged

B. Response time: 0ms

C. Response time: NaN

D. Response time: 150ms

Solution

1. Step 1: Understand timer start and finish

   The timer starts at request start and logs when response finishes, so it measures full duration.

2. Step 2: Calculate logged time

   If request takes 150ms, logged time is approximately 150ms.

3. Final Answer:

   Response time: 150ms -> Option D

4. Quick Check:

   Timer logs actual elapsed time on 'finish' event [OK]

Hint: Logs time difference on response finish event [OK]

Common Mistakes:

• Assuming log happens immediately (0ms)
• Confusing timer start and end
• Expecting no output without console.log

4. Why does this middleware fail to log correct response time?

app.use((req, res, next) => {
  const start = Date.now();
  console.log(Date.now() - start);
  next();
});

medium

A. It logs after response ends, so time is too long

B. It logs before response finishes, so time is near zero

C. It uses wrong event to measure time

D. It does not call next(), so request hangs

Solution

1. Step 1: Analyze when logging happens

   Logging happens immediately after start, before response finishes, so duration is near zero.

2. Step 2: Check middleware flow

   next() is called, so request continues; no wrong event used; logging is too early.

3. Final Answer:

   It logs before response finishes, so time is near zero -> Option B

4. Quick Check:

   Log after response finish for correct timing [OK]

Hint: Log after response finishes, not before [OK]

Common Mistakes:

• Logging too early before response ends
• Forgetting to call next() (not here though)
• Using wrong event to measure time

5. You want to log slow requests taking over 500ms in Express. Which code correctly implements this?

hard

A. app.use((req, res) => { if (Date.now() > 500) console.log('Slow request'); });

B. app.use((req, res, next) => { const start = Date.now(); if (Date.now() - start > 500) console.log('Slow request'); next(); });

C. app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); });

D. app.use((req, res, next) => { console.log('Slow request'); next(); });

Solution

1. Step 1: Understand timing and event usage

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); }); measures time from request start to response finish, then checks if duration > 500ms.

2. Step 2: Check other options

   Other options either check time immediately (always near zero), use wrong conditions like Date.now() > 500, or log unconditionally for all requests.

3. Final Answer:

   app.use((req, res, next) => { const start = Date.now(); res.on('finish', () => { if (Date.now() - start > 500) console.log('Slow request'); }); next(); }); -> Option C

4. Quick Check:

   Check duration on 'finish' event, then log if slow [OK]

Hint: Check time after response finishes, then log if slow [OK]

Common Mistakes:

• Checking time too early (before response ends)
• Logging all requests as slow
• Not using 'finish' event to measure full duration