---
id: 675e8133c874a588f947de57
title: Task 75
challengeType: 19
dashedName: task-75
lang: en-US
---

<!-- READING -->

# --instructions--

Read the text and answer the question below.

# --questions--

## --text--

Mark spoke to the team about the importance of solving login problems and keeping users satisfied:

`Team, user authentication is one of the most critical parts of our system, isn't it? When users start complaining about login issues, we need to investigate session management and check if the tokens are being refreshed properly. If the tokens aren't renewed on time, users may lose access or face frustrating errors, and we don't want that, do we?`

`The first step is to analyze the server logs. If we can't find the cause in the logs, the next step is to replicate the issue on a staging server. Testing on a staging server is safe because it allows us to try different solutions without affecting the live system.`

`When login problems continue, support tickets will start piling up, won't they? Solving these issues quickly is not just about fixing the system — it's also about maintaining user trust and satisfaction, isn't it? Let's work together, find the root cause, and resolve this problem efficiently.`

What does Mark suggest if the server logs don't show the cause of the problem?

## --answers--

Ignore the issue until more support tickets are filed.

### --feedback--

Ignoring the issue delays problem resolution and increases user frustration, which is not what Mark suggests.

---

Replicate the issue on the staging server.

---

Test solutions directly on the live system.

### --feedback--

Testing solutions directly on the live system risks further disruptions for users, which Mark advises against.

---

Wait for users to stop complaining.

### --feedback--

Mark does not suggest waiting for users to stop complaining. He emphasizes proactive troubleshooting instead.

## --video-solution--

2

# --explanation--

To find the correct answer, refer to Mark's suggestion in the text.

He advises replicating the issue on the staging server when the logs don't provide enough information. This allows safe testing of solutions without affecting the live system.
