Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

F5 Networks Exam 301b Topic 3 Question 66 Discussion

Actual exam question for F5 Networks's 301b exam
Question #: 66
Topic #: 3
[All 301b Questions]

A client is attempting to log in to a web application that requires authentication. The following HTTP headers are sent by the client:

GET /owa/ HTTP/1.1

Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=

User-Agent: curl/7.26.0

Host: 10.0.0.14

Accept: */*

Accept-EncodinG. gzip,deflate

The web server is responding with the following HTTP headers:

HTTP/1.1 401 Unauthorized

Content-TypE. text/html

Server: Microsoft-IIS/7.5

WWW-AuthenticatE. NTLM

DatE. Wed, 16 Aug 1977 19:12:31 GMT

Content-LengtH. 1293

The client has checked the login credentials and believes the correct details are being entered.

What is the reason the destination web server is sending an HTTP 401 response?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Charlena
16 days ago
The server is like, 'Nope, not today!' with that 401 Unauthorized. The client needs to upgrade their authentication game if they want to get past those IIS guards.
upvoted 0 times
Lauran
15 hours ago
A) The username and password are incorrect.
upvoted 0 times
...
...
Marya
1 months ago
Haha, the client is using 'curl/7.26.0' to authenticate. I bet the developers are scratching their heads, wondering why it's not working. Basic auth won't fly with that NTLM-loving server!
upvoted 0 times
Abel
3 days ago
C: The client needs to switch to NTLM authentication to access the web application.
upvoted 0 times
...
Sharan
4 days ago
B: That's why it's responding with a 401 Unauthorized status.
upvoted 0 times
...
Tequila
16 days ago
A: The destination web server is expecting NTLM authentication, not Basic auth.
upvoted 0 times
...
...
Venita
1 months ago
Oh, this is a classic case of the server and client not seeing eye to eye on authentication. The server wants NTLM, but the client is trying Basic. Time to update the client to use the right method!
upvoted 0 times
Kimberlie
13 hours ago
Server: Yes, that should resolve the issue.
upvoted 0 times
...
Ena
2 days ago
Client: Oh, so I need to switch to NTLM instead of Basic?
upvoted 0 times
...
Levi
8 days ago
Server: The wrong authentication mechanism is being used.
upvoted 0 times
...
Carlee
20 days ago
Client: Why am I getting a 401 Unauthorized response from the server?
upvoted 0 times
...
...
Cornell
2 months ago
Hmm, the server is expecting NTLM authentication, but the client is using Basic. Looks like a mismatch in the authentication protocol. Basic won't cut it here.
upvoted 0 times
Yuki
20 days ago
Server: Yes, it looks like the client is using Basic instead of NTLM.
upvoted 0 times
...
Thaddeus
28 days ago
Client: I think the server is expecting a different authentication method.
upvoted 0 times
...
...
Nathan
2 months ago
So, the client needs to update the authentication method to match what the server is expecting to successfully log in.
upvoted 0 times
...
Eloisa
2 months ago
The 401 Unauthorized response indicates that the authentication mechanism being used is not the one expected by the server. The headers show the client is using Basic authentication, but the server is expecting NTLM authentication.
upvoted 0 times
Giovanna
18 days ago
D: The server is not recognizing the Basic authentication.
upvoted 0 times
...
Karol
20 days ago
C: The client needs to switch to NTLM authentication.
upvoted 0 times
...
Marci
22 days ago
B: The server is expecting NTLM authentication.
upvoted 0 times
...
Jamal
26 days ago
A: The wrong authentication mechanism is being used.
upvoted 0 times
...
...
Fairy
2 months ago
I agree with Rodrigo. The server is expecting NTLM authentication, but the client is sending Basic authentication.
upvoted 0 times
...
Rodrigo
2 months ago
I think the reason for the 401 response is because the wrong authentication mechanism is being used.
upvoted 0 times
...

Save Cancel