Exam AZ-301 topic 11 question 1 discussion

Maintenance of the database is performed by using SQL Server Agent jobs. Should it be managed instance

Why not a. an Azure SQL Database managed instance? Managed instance would be compatible with existing on-premise SQL Server features and it would meet the requirement to minimise the effort required to modify the middle tier and backend tier of the payment processing system

A. an Azure SQL Database managed instance

A is correct answer.

should be A for sure

As already serval times mentioned above, the key is "SQL Agents" are not supported on Azure Single DB, they are only supported on Managed Instance. I can recommend the following Ignite Video as a comparison: See: at Time 11:08 (no SQL Agent support for MS SQL Single DB) and time 15.31 SQL Agent Support for Managed Instance. Managed Instance is the Azure Solution for "almost" an On Premise DB, without the general limitations. Ref: https://azure.microsoft.com/en-us/resources/videos/ignite-2018-azure-sql-database-managed-instance-comparison-to-azure-sql-database/

One of the requirement is: "Support blocking inbound and outbound traffic based on the source IP address, the destination IP address, and the port number." I think this can not be achieved by SQL Server Firewall hence we need NSG. That is why best option look like Azure Managed Instance.

“Using SQL Server Agent jobs” is talking about existing environment right? And the question is about implementing a new solution - so why bother?

A. an Azure SQL Database managed instance - Does support "SQL Agent Jobs" B. a SQL Server database on an Azure virtual machine - Can be ruled out, as the technical requirements say to use a PaaS whenever possible C. an Azure SQL Database single database - Can be ruled out, as it doesn't support "SQL Agent Jobs" D. an Azure SQL Database elastic pool - There is only one production database so no added value when using elastic pools => Conclusion: Answer A)

"Minimize the effort required to modify the middle-tier API and the back-end tier of the payment processing system" this can be achieved only using managed instance which is nearly a 100% compatibility to on-prem and needs no to almost no changes.

C. an Azure SQL Database single database

I thinks it should be: B As mentioned on the question that "The middle-tier API uses the Entity Framework to communicate to the SQL Server database. Maintenance of the database is performed by using SQL Server Agent jobs." And here's the list of supported DBs under Entity framework: https://docs.microsoft.com/en-us/ef/core/providers/?tabs=dotnet-core-cli Apart from supported Azure DBs, it support directly only "Azure Cosmos DB SQL API" or any normal SQL 2012 DB or above that's why i recommend "B".

Now LTR is supported for SQL Managed Instance. https://docs.microsoft.com/en-us/azure/sql-database/sql-database-long-term-retention#managed-instance-support

Do we have to consider 'Support blocking inbound and outbound traffic based on the source IP address, the destination IP address, and the port number.'? Does SQL server managed instance support it?

Answer should be A… Migration Requirements ;- Whenever possible, Azure managed services must be used to minimize management overhead.

I believe the answer to be Azure SQL Database managed instance for a number of reasons. Reason 1 - Minimize the effort required to modify the middle-tier API and the back-end tier of the payment processing system. Managed instance gives most of the features of an on premise SQL server. Reason 2 - Keep backups of the data in two separate physical locations that are at least 200 miles apart and can be restored for up to seven years. Managed instances support T-SQL backup database statements. Copy_only backups are supported and can be backed up to blob storage that is geo-replicated, it will remain there till deleted

Encrypt data in transit and rest supports SQL database and sql server