MENU
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?
Suggested Answer: D
Get Premium 301b Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
41 comments · newest first
JA
Janey
12 months ago
Nah, it's probably just the wrong username/password combo.
NI
Nieves
12 months ago
Wait, is the server date really from 1977?
TR
Tran
12 months ago
I thought Basic auth would work too, that's weird.
ME
Melissa
1 year ago
Definitely a mismatch in authentication methods.
AR
Argelia
1 year ago
The server is expecting NTLM, not Basic auth.
JA
Janessa
1 year ago
I recall that using the wrong browser could affect how authentication is handled, but I don't think that's the main reason for a 401 in this case.
MA
Margarita
1 year ago
I'm a bit confused about the date in the response. Could an incorrect server date really cause a 401 error? I thought that was more related to SSL issues.
DE
Desmond
1 year ago
I think we had a practice question about authentication methods, and it mentioned that the server might require a specific type like NTLM, which could be why it's rejecting the request.
JE
Jettie
1 year ago
I remember studying HTTP status codes, and 401 usually means unauthorized access, but I'm not sure if it's always due to incorrect credentials.
NA
Nana
1 year ago
Hmm, this is a tricky one. The configuration has some OSPF settings, but I'm not sure how to interpret them in the context of the question. I'll need to think this through step-by-step.
LI
Lisha
1 year ago
Hmmm... SAML and generic SSO both sound relevant. I'll mark both and hope for the best - this one's tricky.
MA
Marjory
1 year ago
Hmm, the output in the image looks like it's identifying entities in the text. I'm leaning towards option A, entity recognition, but I want to double-check the other options just to be sure.
NA
Nathalie
1 year ago
This seems straightforward. The marital deduction applies to the assets left to the wife, so it's just the listed securities and other securities, right?
CH
Charlena
1 year 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.
VE
Velda
1 year ago
D) The wrong authentication mechanism is being used.
GA
Gary
1 year ago
B) The server has an incorrect date configured.
LA
Lauran
1 year ago
A) The username and password are incorrect.
MA
Marya
1 year 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!
AB
Abel
1 year ago
C: The client needs to switch to NTLM authentication to access the web application.
SH
Sharan
1 year ago
B: That's why it's responding with a 401 Unauthorized status.
TE
Tequila
1 year ago
A: The destination web server is expecting NTLM authentication, not Basic auth.
VE
Venita
2 years 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!
CR
Cristy
1 year ago
Server: Yes, that should resolve the issue.
FR
Francesco
1 year ago
Client: Oh, so I need to switch to NTLM instead of Basic?
ST
Stephaine
1 year ago
Server: The wrong authentication mechanism is being used.
FR
France
1 year ago
Client: Why am I getting a 401 Unauthorized response from the server?
KI
Kimberlie
1 year ago
Server: Yes, that should resolve the issue.
EN
Ena
1 year ago
Client: Oh, so I need to switch to NTLM instead of Basic?
LE
Levi
1 year ago
Server: The wrong authentication mechanism is being used.
CA
Carlee
1 year ago
Client: Why am I getting a 401 Unauthorized response from the server?
CO
Cornell
2 years 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.
YU
Yuki
1 year ago
Server: Yes, it looks like the client is using Basic instead of NTLM.
TH
Thaddeus
1 year ago
Client: I think the server is expecting a different authentication method.
NA
Nathan
2 years ago
So, the client needs to update the authentication method to match what the server is expecting to successfully log in.
EL
Eloisa
2 years 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.
GI
Giovanna
1 year ago
D: The server is not recognizing the Basic authentication.
KA
Karol
1 year ago
C: The client needs to switch to NTLM authentication.
MA
Marci
1 year ago
B: The server is expecting NTLM authentication.
JA
Jamal
1 year ago
A: The wrong authentication mechanism is being used.
FA
Fairy
2 years ago
I agree with Rodrigo. The server is expecting NTLM authentication, but the client is sending Basic authentication.
RO
Rodrigo
2 years ago
I think the reason for the 401 response is because the wrong authentication mechanism is being used.