{"id":11819,"date":"2026-09-14T12:23:05","date_gmt":"2026-09-14T12:23:05","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=11819"},"modified":"2026-09-14T12:23:05","modified_gmt":"2026-09-14T12:23:05","slug":"microsoft-dp-800-practice-test-questions-and-exam-dumps-part-3-q41-q60","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-800-practice-test-questions-and-exam-dumps-part-3-q41-q60\/","title":{"rendered":"Microsoft DP-800 Practice Test Questions and Exam Dumps Part 3: Q41\u2013Q60"},"content":{"rendered":"<h2><b>View Full\u00a0<a href=\"https:\/\/www.examlabs.com\/dp-800-exam-dumps\">Microsoft DP-800 Exam Dumps<\/a>\u00a0and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 41<\/b><\/h3>\n<p><b>Which SQL Server object is commonly used to store a precompiled set of SQL statements and procedural logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">View<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stored procedure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Synonym<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A stored procedure is a database object that contains one or more SQL statements and can include procedural logic. It can accept parameters, perform data modifications, return results, and handle conditional logic. Stored procedures are useful for centralizing database operations and reducing repeated SQL code in applications. They can also help control permissions because users may be given permission to execute a procedure without receiving direct access to underlying tables. Good parameter handling is important for security and reliability.<\/span><\/p>\n<h3><b>Question 42<\/b><\/h3>\n<p><b>Which SQL Server command can display the definition of a stored procedure?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_helptext<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">showprocedure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">procedure_definition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GET PROCEDURE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">sp_helptext<\/span><span style=\"font-weight: 400;\"> can display the text definition of programmable objects such as stored procedures, views, and functions when the caller has appropriate permissions. It is useful when administrators need to inspect existing database logic. The procedure definition can help identify joins, filters, parameters, and other operations that may affect behavior or performance. Administrators should avoid changing production code directly without proper testing and change management.<\/span><\/p>\n<h3><b>Question 43<\/b><\/h3>\n<p><b>Which SQL Server object can return a scalar value or a table based on parameters and defined logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Trigger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Constraint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A SQL Server function is a programmable database object that returns a value or a table. Scalar functions return a single value, while table-valued functions return a result set that can be queried like a table. Functions are useful for reusable calculations and data transformations. However, some functions can introduce performance overhead when used extensively, especially in large queries. Administrators should understand how a function is executed and consider its impact when tuning database workloads.<\/span><\/p>\n<h3><b>Question 44<\/b><\/h3>\n<p><b>Which type of SQL Server function returns a table that can be used in a query&#8217;s FROM clause?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scalar function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table-valued function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Trigger function<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Aggregate-only function<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A table-valued function returns a table result and can be referenced in a query much like a regular table or view. It can accept parameters and provide reusable query logic. Table-valued functions are useful when a query needs a parameterized result set. SQL Server supports inline table-valued functions and multi-statement table-valued functions, which have different performance characteristics. Choosing the appropriate type can help maintain both reusable database logic and good query performance.<\/span><\/p>\n<h3><b>Question 45<\/b><\/h3>\n<p><b>Which SQL Server command can display information about a database object such as its columns and related properties?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_help<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">object_info<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">show_object<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">describe_object<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">sp_help<\/span><span style=\"font-weight: 400;\"> system stored procedure provides information about database objects. Depending on the object, it can display details such as columns, data types, indexes, constraints, and other properties. It is useful when an administrator needs to quickly inspect an unfamiliar table or other database object. This can help during troubleshooting and development without requiring the administrator to manually query multiple system catalog views.<\/span><\/p>\n<h3><b>Question 46<\/b><\/h3>\n<p><b>Which system catalog view contains information about columns in database objects?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.columns<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.fields<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.table_columns<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.object_fields<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">sys.columns<\/span><span style=\"font-weight: 400;\"> catalog view contains metadata about columns for objects in the database. It can be joined with other catalog views, such as <\/span><span style=\"font-weight: 400;\">sys.tables<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">sys.objects<\/span><span style=\"font-weight: 400;\">, to obtain more detailed information. System catalog views are useful for database administration, auditing, documentation, and automation. Instead of relying only on graphical tools, administrators can query these views to inspect database metadata and create scripts that work consistently across environments.<\/span><\/p>\n<h3><b>Question 47<\/b><\/h3>\n<p><b>Which SQL Server catalog view provides information about tables in the current database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.database_tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.objects_tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.tablelist<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">sys.tables<\/span><span style=\"font-weight: 400;\"> catalog view provides information about user tables in the current database. It can be joined with other system catalog views to inspect columns, indexes, constraints, and related metadata. For example, administrators can query <\/span><span style=\"font-weight: 400;\">sys.tables<\/span><span style=\"font-weight: 400;\"> when they need to find tables matching a naming pattern. System catalog views are especially useful for automation because they allow administrators to retrieve database structure using T-SQL rather than manually inspecting objects through a graphical interface.<\/span><\/p>\n<h3><b>Question 48<\/b><\/h3>\n<p><b>Which SQL Server command can show currently running requests and their sessions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_who2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">show_sessions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">session_list<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_running<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">sp_who2<\/span><span style=\"font-weight: 400;\"> is a commonly used system stored procedure for viewing information about SQL Server sessions and processes. It can help administrators identify active sessions, blocking situations, login names, databases, and other details. Although modern monitoring methods may provide more detailed information, <\/span><span style=\"font-weight: 400;\">sp_who2<\/span><span style=\"font-weight: 400;\"> remains useful for quick investigation. When a database appears slow, checking active sessions and blocking can help determine whether another workload is causing delays.<\/span><\/p>\n<h3><b>Question 49<\/b><\/h3>\n<p><b>Which SQL Server dynamic management view can provide information about currently executing requests?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.dm_exec_requests<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.dm_running_tasks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.dm_active_queries<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sys.dm_query_sessions<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">sys.dm_exec_requests<\/span><span style=\"font-weight: 400;\"> provides information about requests currently executing in SQL Server. It can help administrators inspect request status, wait information, CPU time, elapsed time, and other details. This is useful when investigating long-running queries, blocking, or resource-related problems. Dynamic management views are powerful troubleshooting tools, but access may require appropriate permissions. Administrators often combine request information with session and SQL text information to understand what a workload is doing.<\/span><\/p>\n<h3><b>Question 50<\/b><\/h3>\n<p><b>What is blocking in SQL Server?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A failed backup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">One session waiting because another session holds a conflicting lock<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A deleted database<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A disabled login<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Blocking occurs when one SQL Server session holds a lock that prevents another session from accessing a resource in the way it requires. The waiting session remains blocked until the conflicting lock is released or the situation changes. Blocking can be normal for short periods, but excessive or long-lasting blocking can cause application delays. Administrators should identify the blocking session, understand the transaction involved, and determine why the lock is being held for so long.<\/span><\/p>\n<h3><b>Question 51<\/b><\/h3>\n<p><b>Which SQL Server feature can automatically detect certain deadlock situations and provide diagnostic information?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Extended Events<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database diagrams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL Agent alerts only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object Explorer<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Extended Events can capture deadlock information and provide useful details about sessions, resources, and statements involved. A deadlock occurs when two or more transactions wait for resources held by each other, creating a cycle that cannot continue. SQL Server detects the condition and chooses a transaction as the deadlock victim. Administrators can analyze the captured information to understand the cause and redesign transactions or access patterns to reduce the chance of repeated deadlocks.<\/span><\/p>\n<h3><b>Question 52<\/b><\/h3>\n<p><b>Which SQL Server isolation behavior allows a transaction to read data that another transaction has modified but not yet committed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SERIALIZABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">READ COMMITTED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">READ UNCOMMITTED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SNAPSHOT<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">READ UNCOMMITTED<\/span><span style=\"font-weight: 400;\"> allows a transaction to read data that may not yet be committed by another transaction. This can result in dirty reads, meaning the application may see values that are later rolled back. The advantage is reduced locking and potentially better concurrency, but the data may not be reliable for important operations. Administrators should use this isolation level only when the application&#8217;s requirements can tolerate inconsistent reads.<\/span><\/p>\n<h3><b>Question 53<\/b><\/h3>\n<p><b>Which SQL Server feature provides row-versioned reads without requiring readers to block writers in many situations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snapshot isolation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table locking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Exclusive locking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema binding<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Snapshot isolation uses row versions to provide transactions with a consistent view of data without requiring the same level of blocking between readers and writers as traditional locking-based approaches. SQL Server stores row versions in a version store so readers can access the appropriate version of a row. Snapshot-based approaches can improve concurrency, but they consume additional resources. Administrators should understand version-store usage and workload behavior before enabling or changing isolation settings.<\/span><\/p>\n<h3><b>Question 54<\/b><\/h3>\n<p><b>Which SQL Server feature can automatically maintain historical versions of rows for temporal table queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporal tables<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">History triggers only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Archive indexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Versioned views<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SQL Server temporal tables can automatically maintain historical versions of rows. A system-versioned temporal table keeps current data and historical data so administrators can query how records looked at earlier points in time. This is useful for auditing, reporting, and tracking changes. SQL Server manages the history based on system time, reducing the need to build custom triggers for basic history tracking. Administrators should still plan storage because historical records can grow significantly over time.<\/span><\/p>\n<h3><b>Question 55<\/b><\/h3>\n<p><b>Which SQL Server feature can help protect sensitive column values by encrypting data in the database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Always Encrypted<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL Formatter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query Encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table Compression<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Always Encrypted is a SQL Server feature designed to protect sensitive data by keeping selected column values encrypted. Encryption and decryption can occur through supported client drivers, reducing the ability of database administrators or other unauthorized parties to view plaintext values. This is useful for sensitive information such as financial or personal data. Implementing Always Encrypted requires careful planning because encrypted columns can have limitations for searching, indexing, and supported operations.<\/span><\/p>\n<h3><b>Question 56<\/b><\/h3>\n<p><b>Which SQL Server security principle gives a user only the permissions needed to perform their job?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Open access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Least privilege<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shared administration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full control<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Least privilege means giving users and applications only the permissions they actually need. This reduces the possible impact of compromised credentials, accidental changes, and misuse of database resources. In SQL Server, administrators can use roles and specific permissions rather than giving users broad administrative rights. For example, an application may need permission to execute certain stored procedures without needing direct access to every table. Least privilege is a core principle of secure database administration.<\/span><\/p>\n<h3><b>Question 57<\/b><\/h3>\n<p><b>Which SQL Server database role provides broad administrative permissions across the SQL Server instance?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db_datareader<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db_owner<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">public<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db_executor<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">db_owner<\/span><span style=\"font-weight: 400;\"> role provides extensive permissions within a specific database, allowing members to perform most database-level operations. It should be assigned carefully because users in this role have much broader privileges than ordinary application users. The <\/span><span style=\"font-weight: 400;\">public<\/span><span style=\"font-weight: 400;\"> role applies to all database users but has much more limited permissions by default. Roles such as <\/span><span style=\"font-weight: 400;\">db_datareader<\/span><span style=\"font-weight: 400;\"> and <\/span><span style=\"font-weight: 400;\">db_datawriter<\/span><span style=\"font-weight: 400;\"> provide narrower access. Using the least-privilege approach helps reduce unnecessary administrative access.<\/span><\/p>\n<h3><b>Question 58<\/b><\/h3>\n<p><b>Which SQL Server permission allows a user to execute a stored procedure?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EXECUTE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RUN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CALL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PROCESS<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">EXECUTE<\/span><span style=\"font-weight: 400;\"> permission allows a user or role to execute programmable objects such as stored procedures and certain functions. Granting EXECUTE on a stored procedure can be part of a secure database design where applications interact with data through controlled procedures instead of receiving direct table permissions. This supports least privilege and can centralize business logic. Administrators should grant permissions at the narrowest practical scope rather than giving users unnecessary database-wide privileges.<\/span><\/p>\n<h3><b>Question 59<\/b><\/h3>\n<p><b>Which command can grant a SQL Server permission to a user or role?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALLOW<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GRANT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PERMIT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AUTHORIZE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">GRANT<\/span><span style=\"font-weight: 400;\"> statement gives a specified permission to a database principal such as a user or role. For example, <\/span><span style=\"font-weight: 400;\">GRANT SELECT ON dbo.Customers TO SalesRole<\/span><span style=\"font-weight: 400;\"> allows members of SalesRole to read the Customers table. Permissions can be granted at different levels depending on the security design. Administrators should avoid granting broader permissions than necessary. Regular permission reviews are also important because users may accumulate access over time as their responsibilities change.<\/span><\/p>\n<h3><b>Question 60<\/b><\/h3>\n<p><b>Which SQL Server statement removes a previously granted permission from a user or role while leaving the principal available?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DENY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DELETE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REVOKE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REMOVE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">REVOKE<\/span><span style=\"font-weight: 400;\"> statement removes a previously granted or denied permission from a principal. It does not delete the user or role. <\/span><span style=\"font-weight: 400;\">DENY<\/span><span style=\"font-weight: 400;\"> is different because it explicitly prevents a permission, and its behavior can take precedence over some grants depending on the security context. Administrators should understand the SQL Server permission hierarchy before changing access. Regularly reviewing and removing unnecessary permissions supports least privilege and reduces security risk.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full\u00a0Microsoft DP-800 Exam Dumps\u00a0and Practice Test Dumps. &nbsp; Question 41 Which SQL Server object is commonly used to store a precompiled set of SQL statements and procedural logic? View Stored procedure Index Synonym Correct Answer: 2 Explanation A stored procedure is a database object that contains one or more SQL statements and can include [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11819"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=11819"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11819\/revisions"}],"predecessor-version":[{"id":11820,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11819\/revisions\/11820"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=11819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=11819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=11819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}