READ Free Dumps For Microsoft- 70-486
| Question ID 14732 | You are developing an ASP.NET MVC application in a web farm. The application has a
page that accepts a customers order, processes it, and then redirects the browser to a
page where the order is displayed along with the shipping information.
The order information should be available only to the page where the order is displayed.
You need to store state and configure the application.
What should you do? To answer, drag the appropriate item to the correct location. Each
item may be used once, more than once, or not at all. You may need to drag the split bar
between panes or scroll to view content.
|
| Option A | 
|
| Correct Answer | A |
Explanation
| Question ID 14733 | You are developing an ASP.NET MVC application that uses forms authentication. The
application uses SQL queries that display customer order data.
Logs show there have been several malicious attacks against the servers.
You need to prevent all SQL injection attacks from malicious users against the application.
How should you secure the queries?
|
| Option A | Check the input against patterns seen in the logs and other records.
|
| Option B | Escape single quotes and apostrophes on all string-based input parameters.
|
| Option C | Implement parameterization of all input strings.
|
| Option D | Filter out prohibited words in the input submitted by the users.
|
| Correct Answer | C |
Explanation Explanation: SQL Injection Prevention, Defense Option 1: Prepared Statements (Parameterized Queries) The use of prepared statements (aka parameterized queries) is how all developers should first be taught how to write database queries. They are simple to write, and easier to understand than dynamic queries. Parameterized queries force the developer to first define all the SQL code, and then pass in each parameter to the query later. This coding style allows the database to distinguish between code and data, regardless of what user input is supplied. Prepared statements ensure that an attacker is not able to change the intent of a query, even if SQL commands are inserted by an attacker. Reference: SQL Injection Prevention Cheat Sheet