Reference Working with Queued Components

Reference working with queued components

This preview shows page 47 - 49 out of 182 pages.

Reference: Working with Queued Components, -us/dnadvnet/html/vbnet10222002.aspIncorrect Answers A,B,D: All the other suggestions will not be able to use a maximum of two concurrent TCP/IP connections reliably. Question: 12 You need to ensure that the security implementation for the customer Web site meets the requirements of Fabrikam, Inc. Which strategy should you use? A. Use SSL to secure the logon page and customer order pages B. Encrypt the customer category data and the product pricing data in the database C. Encrypt only the customer category data in the database D. Use SSL to secure only the logon page Answer: A Explanation: The order pages must be secured as well. Question: 13 You need to select a user authentication mechanism for the new customer Web site. Which mechanism should you use?
Background image
Exam Name: Analyzing Requirements and Defining Microsoft .Net Solution Architectures Exam Type: Microsoft Exam Code: 70-300 Section Name: Case Studies + Practice Questions Section No: A, B Case Studies: 16 Total Questions: 251 Page 48 of 182 Note: ASP.NET Authentication Providers and IIS Security ASP.NET implements authentication using authentication providers, which are code modules that verify credentials and implement other security functionality such as cookie generation. ASP.NET supports the following three authentication providers: Forms Authentication. Using this provider causes unauthenticated requests to be redirected to a specified HTML form using client side redirection. The user can then supply logon credentials, and post the form back to the server. If the application authenticates the request (using application-specific logic), ASP.NET issues a cookie that contains the credentials or a key for reacquiring the client identity. Subsequent requests are issued with the cookie in the request headers, which means that subsequent authentications are unnecessary. • Passport Authentication. This is a centralized authentication service provided by Microsoft that offers a single logon facility and membership services for participating sites. ASP.NET, in conjunction with the Microsoft® Passport software development kit (SDK), provides similar functionality as Forms Authentication to Passport users. • Windows Authentication. This provider utilizes the authentication capabilities of IIS. After IIS completes its authentication, ASP.NET uses the authenticated identity's token to authorize access. Authentication using non-Windows accounts If you are planning to authenticate users at the application level, and the users do not have Windows accounts, you will typically configure IIS to use Anonymous authentication. In this configuration, consider the following .NET authentication modules:
Background image
Image of page 49

You've reached the end of your free preview.

Want to read all 182 pages?

  • Spring '16
  • Unit testing, .NET Framework, Microsoft SQL Server, Microsoft Visual Studio

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture