{"id":11851,"date":"2026-09-14T12:35:47","date_gmt":"2026-09-14T12:35:47","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=11851"},"modified":"2026-09-14T12:35:47","modified_gmt":"2026-09-14T12:35:47","slug":"microsoft-dp-800-practice-test-questions-and-exam-dumps-part-19-q361-q380","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-800-practice-test-questions-and-exam-dumps-part-19-q361-q380\/","title":{"rendered":"Microsoft DP-800 Practice Test Questions and Exam Dumps Part 19: Q361\u2013Q380"},"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 361<\/b><\/h3>\n<p><b>Which Azure SQL feature allows read-only queries to be routed to a readable secondary replica?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Read scale-out<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transparent Data Encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Data Masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row-Level Security<\/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;\">Read scale-out allows supported Azure SQL workloads to send read-only queries to secondary replicas instead of placing all read workload on the primary replica. This can help improve performance for applications with significant read traffic. The application or connection must use the appropriate read-only routing configuration. Read scale-out is different from disaster recovery because its main purpose is to provide additional read capacity rather than simply serving as a backup for the primary database.<\/span><\/p>\n<h3><b>Question 362<\/b><\/h3>\n<p><b>Which connection string setting indicates that an application intends to perform read-only operations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ApplicationIntent=ReadOnly<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ApplicationMode=Backup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ReadOnly=TrueOnly<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DatabaseIntent=Secondary<\/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;\">ApplicationIntent=ReadOnly<\/span><span style=\"font-weight: 400;\"> tells the SQL client that the application intends to perform read-only operations. In supported Azure SQL configurations, this setting can help route read-only workloads to readable secondary replicas. It is commonly used with read scale-out or availability configurations where secondary replicas are available for read workloads. The setting does not make a user automatically read-only; database permissions and the actual application behavior still determine what operations are allowed.<\/span><\/p>\n<h3><b>Question 363<\/b><\/h3>\n<p><b>Which Azure SQL feature provides a read-only endpoint for accessing a readable secondary replica in supported configurations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Read-only routing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Firewall<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query Store<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQL Server Agent<\/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;\">Read-only routing allows connections that indicate read-only intent to be directed to an appropriate readable secondary replica when the Azure SQL configuration supports this capability. This can reduce read workload on the primary database. Applications typically use the appropriate connection string settings to indicate their intent. Administrators should verify that the selected service and configuration support readable replicas before designing an application around read-only routing.<\/span><\/p>\n<h3><b>Question 364<\/b><\/h3>\n<p><b>Which Azure SQL Database capability allows a database to continue serving read workloads from a secondary replica while the primary database is handling write workloads?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Read scale-out<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database shrinking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transparent Data Encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Data Masking<\/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;\">Read scale-out provides additional capacity for read-only workloads by allowing queries to use secondary replicas. The primary replica remains responsible for write operations while supported read workloads can be distributed to readable replicas. This can be helpful for applications such as reporting systems, dashboards, and analytical queries that generate significant read traffic. Administrators should evaluate workload patterns before enabling or depending on read scale-out because not every query or application scenario benefits from it.<\/span><\/p>\n<h3><b>Question 365<\/b><\/h3>\n<p><b>Which SQL Server database file normally stores transaction log information?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.mdf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.ndf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.ldf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.bak<\/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;\">.ldf<\/span><span style=\"font-weight: 400;\"> file is the standard SQL Server transaction log file. It records transaction activity needed for recovery and other database operations. The primary data file normally uses the <\/span><span style=\"font-weight: 400;\">.mdf<\/span><span style=\"font-weight: 400;\"> extension, while additional data files commonly use <\/span><span style=\"font-weight: 400;\">.ndf<\/span><span style=\"font-weight: 400;\">. Backup files commonly use <\/span><span style=\"font-weight: 400;\">.bak<\/span><span style=\"font-weight: 400;\">. Administrators should monitor transaction log growth because an improperly managed log can consume available storage and affect database operations.<\/span><\/p>\n<h3><b>Question 366<\/b><\/h3>\n<p><b>Which SQL Server file extension is normally associated with the primary database data file?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.ldf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.mdf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.trn<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.bak<\/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;\">.mdf<\/span><span style=\"font-weight: 400;\"> extension is commonly used for the primary data file of a SQL Server database. It contains database data and database objects such as tables and indexes. Additional data files commonly use the <\/span><span style=\"font-weight: 400;\">.ndf<\/span><span style=\"font-weight: 400;\"> extension, while transaction log files use <\/span><span style=\"font-weight: 400;\">.ldf<\/span><span style=\"font-weight: 400;\">. Backup files may use extensions such as <\/span><span style=\"font-weight: 400;\">.bak<\/span><span style=\"font-weight: 400;\"> or <\/span><span style=\"font-weight: 400;\">.trn<\/span><span style=\"font-weight: 400;\">. Administrators should understand these file types when managing storage, configuring file growth, troubleshooting capacity problems, or planning database migrations.<\/span><\/p>\n<h3><b>Question 367<\/b><\/h3>\n<p><b>Which SQL Server file extension is commonly used for an additional secondary data file?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.ndf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.ldf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.mdf<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">.bak<\/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;\">.ndf<\/span><span style=\"font-weight: 400;\"> extension is commonly used for secondary or additional data files in SQL Server databases. A database can have multiple data files when additional storage or specific storage layouts are required. The primary data file normally uses <\/span><span style=\"font-weight: 400;\">.mdf<\/span><span style=\"font-weight: 400;\">, while transaction log files use <\/span><span style=\"font-weight: 400;\">.ldf<\/span><span style=\"font-weight: 400;\">. Administrators can configure filegroups and multiple data files to organize storage, but simply adding files does not automatically improve performance unless the storage and workload design benefit from the configuration.<\/span><\/p>\n<h3><b>Question 368<\/b><\/h3>\n<p><b>Which SQL Server command can be used to view database file information?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DBCC SHRINKDATABASE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">FILEPROPERTY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_helpfile<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BACKUP DATABASE<\/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;\">sp_helpfile<\/span><span style=\"font-weight: 400;\"> displays information about the files associated with the current database, including file names, sizes, maximum sizes, and growth settings. It can help administrators inspect how database storage is configured. This is useful when investigating storage consumption or planning changes to database files. <\/span><span style=\"font-weight: 400;\">DBCC SHRINKDATABASE<\/span><span style=\"font-weight: 400;\"> is instead related to shrinking database files, which should not be performed routinely because unnecessary shrinking can lead to fragmentation and repeated file growth.<\/span><\/p>\n<h3><b>Question 369<\/b><\/h3>\n<p><b>Which command can be used to view database filegroups and their associated files?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">sp_helpfilegroup<\/span><\/li>\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;\">sp_helptext<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DBCC CHECKDB<\/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_helpfilegroup<\/span><span style=\"font-weight: 400;\"> provides information about the filegroups defined in the current database. Filegroups are logical containers used to organize database data files. They can help administrators manage storage layouts and, in some designs, control where database objects are stored. <\/span><span style=\"font-weight: 400;\">sp_who2<\/span><span style=\"font-weight: 400;\"> is used for session and process information, while <\/span><span style=\"font-weight: 400;\">sp_helptext<\/span><span style=\"font-weight: 400;\"> displays the definition of programmable objects. Understanding filegroups is useful when managing large databases and planning storage configurations.<\/span><\/p>\n<h3><b>Question 370<\/b><\/h3>\n<p><b>Which action is generally recommended when a SQL Server transaction log repeatedly grows because transactions are not being backed up?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use appropriate transaction log backups<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable all database indexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delete the .ldf file<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shrink the database every minute<\/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;\">In the Full or Bulk-logged recovery model, regular transaction log backups are important for managing log reuse and supporting point-in-time recovery. If log backups are not being performed, the transaction log can continue growing as log space cannot be reused for the expected recovery process. Administrators should identify the actual reason for log growth before taking action. Deleting the log file is not a valid solution, and frequent shrinking is generally discouraged.<\/span><\/p>\n<h3><b>Question 371<\/b><\/h3>\n<p><b>Which database recovery model generally does not support point-in-time recovery through transaction log backups?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bulk-logged<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Simple<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Enterprise<\/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 Simple recovery model automatically reuses transaction log space after transactions are no longer needed for recovery, reducing the need for transaction log backups. Because transaction log backups are not supported in the Simple recovery model, it does not provide traditional point-in-time recovery through a sequence of log backups. Full recovery is used when point-in-time recovery is required. Administrators should select a recovery model based on recovery objectives and workload requirements.<\/span><\/p>\n<h3><b>Question 372<\/b><\/h3>\n<p><b>Which SQL Server recovery model is typically selected when an organization requires point-in-time recovery using transaction log backups?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Simple<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Read-only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Offline<\/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 Full recovery model supports transaction log backups and allows administrators to restore a database to a specific point in time when an appropriate backup chain is available. This makes it suitable for systems with strict recovery requirements. Administrators must perform regular log backups to prevent unnecessary log growth and maintain the recovery chain. Full recovery alone does not guarantee recovery; successful backups and proper restore procedures must also be maintained and tested.<\/span><\/p>\n<h3><b>Question 373<\/b><\/h3>\n<p><b>What is the main purpose of a database compatibility level in SQL Server and Azure SQL?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To control database backup encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To influence database engine behavior and feature compatibility<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To create database users<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To allocate additional storage automatically<\/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;\">Database compatibility level controls certain database engine behaviors and allows applications to run with behavior associated with a selected SQL Server version level. It can be useful when migrating databases to a newer SQL platform because administrators can separate the database engine upgrade from some application behavior changes. Compatibility level does not change the physical database version itself. Administrators should test applications and queries before changing compatibility level in production.<\/span><\/p>\n<h3><b>Question 374<\/b><\/h3>\n<p><b>Which command can be used to change the compatibility level of a SQL Server database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER DATABASE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER LOGIN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER INDEX<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER SERVER<\/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;\">ALTER DATABASE<\/span><span style=\"font-weight: 400;\"> statement can be used to change various database-level settings, including compatibility level. For example, an administrator can specify a supported compatibility level using an <\/span><span style=\"font-weight: 400;\">ALTER DATABASE<\/span><span style=\"font-weight: 400;\"> command. Changing compatibility level may affect query optimization and certain database behaviors, so testing is recommended before applying the change to production. Administrators should verify that the selected compatibility level is supported by the SQL platform and appropriate for the application.<\/span><\/p>\n<h3><b>Question 375<\/b><\/h3>\n<p><b>Which database setting can help control whether Query Store collects query information?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query Store state<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Filegroup ownership<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Login policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Firewall mode<\/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;\">Query Store has configuration settings that control whether query, plan, and runtime information is collected. Administrators can enable or disable Query Store and configure settings such as data retention and capture behavior. Query Store is useful for tracking query performance over time and identifying plan changes. Proper configuration helps balance the amount of performance history retained with storage and workload considerations.<\/span><\/p>\n<h3><b>Question 376<\/b><\/h3>\n<p><b>What is one major benefit of Query Store for database administrators?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It permanently encrypts all database files<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It tracks query performance and execution plans over time<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It replaces database backups<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It automatically creates every required database user<\/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;\">Query Store captures query-related information, including execution plans and runtime performance data, allowing administrators to investigate performance changes over time. It can help identify queries whose performance has degraded after a plan change and can support plan forcing when appropriate. Query Store does not replace backups or encryption features. Its main purpose is performance monitoring and troubleshooting at the query level.<\/span><\/p>\n<h3><b>Question 377<\/b><\/h3>\n<p><b>Which feature can automatically correct certain query performance problems by forcing a previously successful execution plan?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Automatic plan correction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic Data Masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Firewall<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transparent Data Encryption<\/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;\">Automatic plan correction can detect certain plan regressions and force a previously known good execution plan when the feature and workload support it. This capability is associated with Azure SQL automatic tuning and Query Store information. It can reduce the need for administrators to manually investigate every plan regression. However, administrators should monitor automatic actions and review recommendations because workload changes may make a previously successful plan less appropriate later.<\/span><\/p>\n<h3><b>Question 378<\/b><\/h3>\n<p><b>Which tool is commonly used to migrate SQL Server schema and database objects as a deployment package?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DACPAC<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JPEG<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TXT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CSV<\/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;\">A DACPAC is a deployment package that represents the schema of a SQL database. It can be used with tools such as SqlPackage to deploy database schema changes to supported SQL platforms. DACPACs are useful for database development and deployment workflows because they help package database structure separately from application code. A DACPAC should not be confused with a BACPAC, which can include both schema and data for database export and import scenarios.<\/span><\/p>\n<h3><b>Question 379<\/b><\/h3>\n<p><b>Which tool can be used to publish a DACPAC to a SQL database?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SqlPackage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Monitor<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Kusto Explorer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Advisor<\/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;\">SqlPackage is a command-line utility that can perform various database deployment and migration operations, including publishing a DACPAC to a target database. It is useful for automated deployment pipelines and database DevOps workflows. Administrators can use SqlPackage to generate scripts, deploy schema changes, and perform other supported database operations. Before deploying changes to production, administrators should validate the package and test its effects on the target environment.<\/span><\/p>\n<h3><b>Question 380<\/b><\/h3>\n<p><b>Which Microsoft tool can assess SQL Server databases and identify potential compatibility or migration issues before moving them to Azure?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data Migration Assistant<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Calculator<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Cost Management<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Azure Storage 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;\">Data Migration Assistant (DMA) can assess SQL Server databases for compatibility issues and provide recommendations before migration to Azure or a newer SQL Server version. It can identify features or behaviors that may require attention during migration. This assessment helps administrators reduce unexpected problems after moving workloads. DMA is different from Azure Cost Management, which focuses on spending, and Azure Storage Explorer, which is primarily used to manage storage resources.<\/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 361 Which Azure SQL feature allows read-only queries to be routed to a readable secondary replica? Read scale-out Transparent Data Encryption Dynamic Data Masking Row-Level Security Correct Answer: 1 Explanation Read scale-out allows supported Azure SQL workloads to send read-only queries to secondary replicas instead [&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\/11851"}],"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=11851"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11851\/revisions"}],"predecessor-version":[{"id":11852,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11851\/revisions\/11852"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=11851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=11851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=11851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}