You need to set up Microsoft SQL Server on GCP. Management requires that there's no downtime in case of a data center outage in any of the zones within a GCP region. What should you do?
A.
Configure a Cloud SQL instance with high availability enabled.
B.
Configure a Cloud Spanner instance with a regional instance configuration.
C.
Set up SQL Server on Compute Engine, using Always On Availability Groups using Windows Failover Clustering. Place nodes in different subnets.
D.
Set up SQL Server Always On Availability Groups using Windows Failover Clustering. Place nodes in different zones.
A seems correct.
"... high availability (HA) configuration for Cloud SQL instances... A Cloud SQL instance configured for HA is also called a regional instance and is located in a primary and secondary zone within the configured region.
In the event of an instance or zone failure, this configuration reduces downtime, and your data continues to be available to client applications."
Actually, although Cloud SQL offers high availability configurations, it currently doesn't support Microsoft SQL Server as one of its managed database engines. It primarily focuses on MySQL, PostgreSQL, and SQL Server (but not the full Microsoft SQL Server). And the question clearly states "you need to set up Microsoft SQL." Very tricky question. The answer is D
It is available, please see;
https://cloud.google.com/sql/docs/sqlserver/high-availability?_ga=2.30855355.-503483612.1582800507
Also a video from Google;
https://youtu.be/vMUpNoukwnM
The problem is that these questions are ancient (talking about StackDriver all the time for example, it was rebranded in 2020!!!). So unfortunately we need to think of "What did the professor think 2-4 years ago" when this question was created. Otherwise I'd say A is the best all day!
D is correct.
Question is - "no downtime while installing MS SQL" , not on choosing or replacing with GCP product. I agree A is good solution for this requirements.. however question is not on choosing database.. its for HA.. so I will choose D.
Cloud SQL with HA is not sufficient because it does not provide the level of control and multi-zone redundancy that Always On Availability Groups on Compute Engine can deliver. Always On is the recommended solution for enterprise-grade high availability and disaster recovery in SQL Server deployments.
Cloud SQL offers high availability configurations, it currently support Microsoft SQL Server
please see;
https://cloud.google.com/sql/docs/sqlserver/high-availability?_ga=2.30855355.-503483612.1582800507
Also a video from Google;
https://youtu.be/vMUpNoukwnM
- HA - has minimal downtime
- windows-server-failover-clustering has zero, but much harder to setup: https://cloud.google.com/compute/docs/tutorials/running-windows-server-failover-clustering
A looks more relevant - Multiple zones (Highly available)
Automatic failover to another zone within your selected region. Recommended for production instances. Increases cost.
The correct approach is: D
Set up SQL Server Always On Availability Groups using Windows Failover Clustering. Place nodes in different zones.
Here’s why this is the best option:
• SQL Server Always On Availability Groups: This solution provides high availability by automatically failing over to another node in the event of a failure. It’s specifically designed for SQL Server and ensures minimal downtime in case of outages.
• Windows Failover Clustering: By configuring Windows Failover Clustering with Always On Availability Groups, you can achieve high availability by ensuring that the SQL Server can failover to another node in case of a zone or node failure.
• Placing nodes in different zones: By deploying nodes in different zones within the same region, you ensure that your setup is protected from any potential zone-level outages. If one zone experiences a failure, the other zone can take over without downtime.
The correct answer is D. Set up SQL Server Always On Availability Groups using Windows Failover Clustering. Place nodes in different zones.
Here’s why:
SQL Server Always On Availability Groups is a high-availability and disaster recovery solution for SQL Server that works across multiple zones, ensuring minimal downtime in case of a data center outage within a region.
By placing the nodes in different zones, you ensure that the database remains accessible even if one zone goes down, meeting the requirement of no downtime in case of a zone failure.
The other options are less suitable for this scenario:
A. Cloud SQL with high availability enabled would not work because Cloud SQL supports MySQL, PostgreSQL, and SQL Server but has limitations for high-availability setups with SQL Server compared to Always On Availability Groups.
B. Cloud Spanner is a Google-native distributed database solution and not directly related to SQL Server.
C mentions using different subnets, but you specifically need to place the nodes in different zones to ensure availability across multiple data centers within a region.
Thus, D is the most accurate solution for ensuring no downtime in the event of a zone failure while using Microsoft SQL Server on GCP.
Cloud SQL for SQL Server is a fully managed relational database service from Google Cloud that allows users to set up, maintain, and manage Microsoft SQL Server databases in the cloud. Cloud SQL also supports MySQL and PostgreSQL
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.
learningpv
Highly Voted 4 years, 11 months agomrealtor
2 years, 8 months agotycho
2 years, 4 months agoRic350
4 months, 2 weeks agodiluviouniv
3 years, 5 months agolearningpv
4 years, 11 months agocetanx
4 years, 6 months agoJos
4 years, 11 months agotocsa
7 months agoAmitAr
2 years, 7 months agoSMS
Highly Voted 4 years, 9 months agoJonathanSJ
Most Recent 3 days, 19 hours agoplumbig11
2 weeks, 6 days agoSrrb20
3 weeks, 3 days agoklayytech
1 month agovalgorodetsky
1 month, 1 week agongeorgiev2
1 month, 3 weeks agoSerGCP
1 month, 3 weeks agosim7243
1 month, 3 weeks agobd311b9
2 months agonareshthumma
2 months, 1 week agoselected
2 months, 1 week agoJohnJamesB1212
3 months, 3 weeks agoJohnJamesB1212
3 months, 3 weeks agodesertlotus1211
5 months agodesertlotus1211
5 months agonhatne
6 months, 1 week agoccpmad
6 months, 3 weeks agohitmax87
7 months, 3 weeks ago