← Back to exam page

70-486 – Developing ASP.NET MVC 4 Web Applications

Loading demo links...

Showing 7–9 of 15 questions

Question 7 (Mixed Questions)

You are designing an enterprise-level Windows Communication Foundation (WCF) application. User accounts will migrate from the existing system. The new system must be able to scale to accommodate the increasing load.

You need to ensure that the application can handle large-scale role changes.

Which two approaches can you use for authorization?

Select all that apply, then click Submit answer.

  • ○

    Resource-based trusted subsystem model
  • ○

    Identity-based approach
  • ○

    Role-based approach
  • ○

    Resource-based impersonation/delegation model
Question 8 (Mixed Questions)

You are developing an ASP.NET MVC application that will be deployed on local Internet Information Services (IIS) servers and on an Azure Web Role.

You must log events for the application when it is deployed locally and on Azure. You must not deploy additional services.

You need to implement a logging solution.

Which two technologies can you use? Each correct answer presents a complete solution.

Select all that apply, then click Submit answer.

  • ○

    event log
  • ○

    trace
  • ○

    console
  • ○

    named pipe
Question 9 (Case Study 3)

You are creating a new authentication system that uses an HTTP header value.

The existing authentication system must continue to operate normally.

You need to implement the custom authentication.

What should you do? (Each correct answer presents a complete solution. Choose all that apply.)

Select all that apply, then click Submit answer.

  • ○

    Create a class derived from ActionResult and check for a valid HTTP header value in the ExecuteResult method. Change all actions to return this new class.
  • ○

    Create an HttpHandler to check fora valid HTTP header value in the ProcessRequest method.
  • ○

    Create an HttpModule and check for a valid HTTP header value in the AuthenticateRequest event.
  • ○

    Create a class derived from AuthorizeAttribute and check for a valid HTTP header value in the AuthorizeCore method. Change usages of the existing AuthorizeAttribute to use the new class.