Instead restore Database1 from Server1 to the Server2 by using the RESTORE Transact-SQL command and the REPLACE option.
Note: REPLACE should be used rarely and only after careful consideration. Restore normally prevents accidentally overwriting a database with a different database. If the database specified in a RESTORE statement already exists on the current server and the specified database family GUID differs from the database family GUID recorded in the backup set, the database is not restored. This is an important safeguard.
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/restore-statements-transact-sql

There are CPU and Data I/O spikes for the PaaS prototype. Business Critical 4-vCore is needed.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/reserved-capacity-overview

Section: [none]
Explanation:
The Max Size (MB) limit isn't strictly enforced. Storage size is checked only when Query Store writes data to
disk. This interval is set by the Data Flush Interval (Minutes) option. If Query Store has breached the maximum
size limit between storage size checks, it transitions to read-only mode.
Incorrect Answers:
C: Statistics Collection Interval: Defines the level of granularity for the collected runtime statistic, expressed in
minutes. The default is 60 minutes. Consider using a lower value if you require finer granularity or less time to
detect and mitigate issues. Keep in mind that the value directly affects the size of Query Store data.
Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/performance/best-practice-with-the-query-store

Section: [none]
Explanation:
Box 1: DTU
Scenario:
* The 30 new databases must scale automatically.
* Once all requirements are met, minimize costs whenever possible.
You can configure resources for the pool based either on the DTU-based purchasing model or the vCore-based
purchasing model.
In short, for simplicity, the DTU model has an advantage. Plus, if you're just getting started with Azure SQL
Database, the DTU model offers more options at the lower end of performance, so you can get started at a
lower price point than with vCore.
Box 2: An Azure SQL database elastic pool
Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple
databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a
single server and share a set number of resources at a set price. Elastic pools in Azure SQL Database enable
SaaS developers to optimize the price performance for a group of databases within a prescribed budget while
delivering performance elasticity for each database.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview
https://docs.microsoft.com/en-us/azure/azure-sql/database/reserved-capacity-overview
Question Set 2

Section: [none]
Explanation:
Scenario: Authenticate database users by using Active Directory credentials.
(Create a new Azure SQL database named ResearchDB1 on a logical server named ResearchSrv01.) Authenticate the user in SQL Database or SQL Data Warehouse based on an Azure Active Directory user:
CREATE USER [[email protected]] FROM EXTERNAL PROVIDER;
Reference:
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-user-transact-sql Question Set 2