The answer is correct since the payment processing system DB is still in SQL and in the requirement this payment processing system has been planned to be migrated to Azure where "Infrastructure services must remain available if a region or a data center fails. Failover must occur without any administrative intervention. Whenever possible, Azure managed services must be used to minimize management overhead. Whenever possible, costs must be minimized. If a data center fails, ensure that the payment processing system remains available without any administrative intervention. 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."
This requirement get satisfied only With Azure SQL Database, you can set a long-term backup retention policy (LTR) to automatically retain backups in separate Azure Blob storage containers for up to 10 years. You can then recover a database using these backups using the Azure portal or PowerShell. Long-term retention policies are also supported for Azure SQL Managed Instance.
Costys must be minimised LTR with geo-reunduancy is not more expansive :
Your LTR storage cost won't increase as backups aren't generated from the secondaries.
https://docs.microsoft.com/en-us/azure/azure-sql/database/long-term-retention-overview?view=azuresql
The backups are only created when the secondary becomes primary.
Correct answer.
On premise has the requirement: 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
Why not Answer A.
One requirement:
Tape backups are configured by using an on-premises deployment of Microsoft System Center Data Protection Manager (DPM), and then shipped offsite for long term storage.
https://docs.microsoft.com/en-us/system-center/dpm/dpm-overview?view=sc-dpm-2019
The answers are confusing, it should have contained Azure Recovery Services Vault as an option not the backup policy type
Backup SQL Server on Azure VM
https://docs.microsoft.com/en-us/azure/backup/backup-sql-server-database-azure-vms#database-naming-guidelines-for-azure-backup
Backup policies
https://docs.microsoft.com/en-us/azure/backup/backup-architecture#sql-server-backup-types
Retention for "monthly", "yearly" backup points is referred to as Long Term Retention (LTR)
Like it says "Database backups must be retained for a minimum of seven years to meet compliance requirements." So Azure backup won´t work you will have to use long term backup that can hold the data up to sevenn years........So Answer is correct
"In Azure SQL Database, you can configure a database with a long-term backup retention policy (LTR) to automatically retain the database backups in separate Azure Blob storage containers for up to 10 years. "
https://docs.microsoft.com/en-us/azure/azure-sql/database/long-term-backup-retention-configure
Here: "Migrate the payment processing system to Azure" ... "Contoso hosts a business-critical payment processing system in its New York data center. The system has three tiers: a front-end web app, a middle-tier web API, and a back-end data store implemented as a Microsoft SQL Server 2014 database. All servers run Windows Server 2012 R2."
https://docs.microsoft.com/en-us/azure/backup/backup-architecture#backup-policy-essentials
I see Azure backup also allowing for long term retention. Maybe the question is old and at that time Azure backup was not the valid choice?
upvoted 1 times
...
...
...
This section is not available anymore. Please use the main Exam Page.AZ-304 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
MaheshS
Highly Voted 3 years, 10 months agonkv
Highly Voted 3 years, 8 months agosapien45
Most Recent 2 years, 11 months agoDpejic
3 years, 4 months agoDpejic
3 years, 4 months agostudent22
3 years, 6 months agosyu31svc
3 years, 7 months agoHank_Qin
3 years, 11 months agorobotcop
4 years agopentium75
3 years, 8 months agoarseyam
4 years, 3 months agoDavid_986969
4 years, 7 months agoDavid_986969
4 years, 7 months agopentum7
4 years, 6 months agoMoley
3 years, 12 months agoEl_Hechizo
3 years, 9 months agoPinto
3 years, 9 months ago