Exam 70-486 topic 1 question 117 discussion

Actual exam question from Microsoft's 70-486

Question #: 117
Topic #: 1

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some questions sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You are developing an ASP.NET Core MVC web application.
The application must be exposed to external users over ports 80 and 443 and must meet the following requirements:
✑ Handle more than 1024 simultaneous connections.
✑ Support Windows authentication.
✑ Support HTTP/2 over TLS.
✑ Include response caching.
✑ Protect against denial-of-service attacks.
You need to deploy the application to an on-premises web server.
Solution: You deploy the application to Kestrel with an IIS reverse proxy.
Does the solution meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: B 🗳️

by Ekovalev at Nov. 14, 2019, 7:54 p.m.

Comments

Submit Cancel

AlexFromGalax

Highly Voted 5 years, 7 months ago

Kestrel does not support Windows Authentication

upvoted 7 times

XXXX

5 years, 4 months ago

https://docs.microsoft.com/en-us/aspnet/core/security/authentication/windowsauth?view=aspnetcore-3.1&tabs=visual-studio "Windows Authentication (also known as Negotiate, Kerberos, or NTLM authentication) can be configured for ASP.NET Core apps hosted with IIS, Kestrel, or HTTP.sys."

upvoted 3 times

ewdlop

4 years, 10 months ago

proably not at the time when asp.net mvc 4

upvoted 1 times

...

rhysabray

Highly Voted 5 years, 3 months ago

The real reason for it not meeting the goal: "Windows Authentication isn't supported with HTTP/2. Authentication challenges can be sent on HTTP/2 responses, but the client must downgrade to HTTP/1.1 before authenticating." Source (In the form of a note on the page): https://docs.microsoft.com/en-us/aspnet/core/security/authentication/windowsauth?view=aspnetcore-3.1&tabs=visual-studio

upvoted 5 times

zimzimzimma

5 years ago

But that's only the authentication part in which the client has to downgrade to HTTP/1.1. One could argue it should be 'yes' since regular requests after authorization or anonymous requests work with HTTP/2 right?

upvoted 2 times

...

Ptu12125

Most Recent 4 years, 5 months ago

‡Kestrel has limited support for HTTP/2 on Windows Server 2012 R2 and Windows 8.1. Support is limited because the list of supported TLS cipher suites available on these operating systems is limited. Ref: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-5.0#:~:text=HTTP%2F2%20support,-HTTP%2F2%20is&text=%E2%80%A1Kestrel%20has%20limited%20support,these%20operating%20systems%20is%20limited.

upvoted 1 times

...

Ekovalev

5 years, 7 months ago

Any clue why Kestrel on Azure Linux VM is not a suitable non-premises solution?

upvoted 2 times

...