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.
If your requirement is NO downtime, Cloud SQL does not meet the standard because of its failover delay. Instead, Always On Availability Groups (AGs) on Compute Engine provide the most reliable, enterprise-grade SQL Server HA solution on GCP.
If your requirement is NO downtime, Cloud SQL does not meet the standard because of its failover delay. Instead, Always On Availability Groups (AGs) on Compute Engine provide the most reliable, enterprise-grade SQL Server HA solution on GCP.
While Cloud SQL for SQL Server does offer high availability options, it does not fully meet the requirements specified in the original query. Here’s why:
1. Cloud SQL for SQL Server with high availability does provide protection against zonal outages, but it is limited to 99.99% availability for Enterprise Plus edition.
2. The original query specifically mentions “no downtime in case of a data center outage in any of the zones within a GCP region.” Cloud SQL’s high availability may still have some minimal downtime during failover.
3. The requirement for Microsoft SQL Server suggests a need for more control and customization than what Cloud SQL offers.
The most appropriate solution that fully addresses the requirements is:
Set up SQL Server Always On Availability Groups using Windows Failover Clustering. Place nodes in different zones (Option D).
D is right. B is wrong as Microsoft SQL not supported by Spanner.
A will have slight downtime when the standby instance is activated. Question clearly stated that no downtime is acceptable.
D is the correct answer.
Although Cloud SQL supports SQL Server but not all features are available. One such feature is Always On Availability Group (AOAG) which ensures HA within a region.
A : https://cloud.google.com/sql/docs/sqlserver/configure-ha
Old answer were absed on the fact that CloudSQL had a partial support of SQL Server.
Now you have the full support, and among them the HA
A should be prefered to D, because if technically it is the same, using the managed services is far better
Answer: D is correct.
Why? While option A (the most voted) would technically work, Option D represents the best practice for deploying SQL Server with high availability in GCP:
Placing nodes in different zones provides true zone redundancy
Always On Availability Groups is Microsoft's recommended solution for SQL Server high availability
Windows Failover Clustering provides automated failover capabilities
This architecture provides both high availability and disaster recovery within a region
Not all regions have multiwriter disk, which is what you'll need incase of setting up SQL HA cluster on IaaS. Cloud SQL HA is the right answer. https://cloud.google.com/sql/docs/sqlserver/high-availability?_ga=2.30855355.-503483612.1582800507#normal
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 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 5 years, 3 months agomrealtor
3 years agotycho
2 years, 8 months agoRic350
8 months, 2 weeks agodiluviouniv
3 years, 9 months agolearningpv
5 years, 3 months agocetanx
4 years, 10 months agoJos
5 years, 3 months agotocsa
11 months agoAmitAr
2 years, 11 months agoSMS
Highly Voted 5 years, 1 month agoizekc
Most Recent 1 month, 2 weeks agocd6aff3
1 month, 3 weeks agocd6aff3
1 month, 3 weeks agojobolesonihal
2 months, 1 week agodavid_tay
2 months, 1 week agoJust_Ninja
2 months, 1 week agobiplabid
2 months, 2 weeks agohpf97
2 months, 4 weeks agoHoussemonline
3 months, 3 weeks agogcloud007
4 months agoJonathanSJ
4 months agoplumbig11
4 months, 2 weeks agoSrrb20
4 months, 3 weeks agoklayytech
5 months agovalgorodetsky
5 months, 1 week ago