Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements.
Your company has a Microsoft SQL Server Always On availability group configured on their Azure virtual machines (VMs).
You need to configure an Azure internal load balancer as a listener for the availability group.
Solution: You create an HTTP health probe on port 1433.
Does the solution meet the goal?
The solution does not meet the goal. In order to configure an Azure internal load balancer as a listener for a SQL Server Always On availability group, a TCP health probe on port 1433 is required. Port 1433 is used for SQL Server Database Engine connections, and an HTTP health probe is not suitable for this purpose.
HTTP(!) health probe on port 1433 sounds ugly, assume NO
It does sound ugly haha your comment made me lol
Took the exam today, 17 Oct. This question came out. Ans: No
No, the solution does not meet the goal. Port 1433 is used by SQL Server for SQL Server Database Engine connections, not HTTP connections. Therefore, creating an HTTP health probe on port 1433 will not work. To configure an Azure internal load balancer as a listener for the availability group, you need to create a TCP health probe on port 1433, which is the default port for SQL Server. So, the correct solution would be to create a TCP health probe on port 1433, not an HTTP health probe. Therefore, the answer is B (No).
No, creating an HTTP health probe on port 1433 does not meet the goal of configuring an Azure internal load balancer as a listener for the SQL Server Always On availability group. In order to configure an Azure internal load balancer as a listener for the availability group, you need to create a TCP health probe on port 1433. SQL Server uses TCP to communicate on port 1433, so a TCP health probe is the appropriate choice to ensure the availability and health of the SQL Server instances in the availability group.
Port 1433 for database connections pool, not for HTTP protocol in health check.
The health probe concept is explained in below video https://youtu.be/iEX1KJOcXVk
pls if anyone has contributor access . can you pls mail the dumps to me at <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="b0c2dfded5def0d2db9ec2c5">[email protected]</a> . Thanks
if anyone has contributor access? can you pls mail the dumps to me at <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="3851564e4c4a0908785f55595154165b5755">[email protected]</a>. Thanks
pls if anyone has contributor access . can you pls mail the dumps to me at <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="bfdec6d0d2d6d4cad18e8affd8d2ded6d391dcd0d2">[email protected]</a>. Thanks
If anyone has contributor access... Can u please mail the dumps to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="3e565f4c4d565f4e4d0d0f0f7e59535f5752105d5153">[email protected]</a>... It will be great help..
Answer B. No Explanation An HTTP health probe on port 1433 would not be appropriate for an SQL Server Always On availability group listener. It is essential to use a TCP health probe on port 59999 to monitor the availability group listener properly.
Always On availability group: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver16
if anyone has contributor access, please please can you send please dumps to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="c4a5a5b6aeb1f1f684a3a9a5ada8eaa7aba9">[email protected]</a>, i dont have money to buy this as needed for new job requirements ...
Hello, please if anyone have contributor access, send full dump to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="94fbe7f7f5e6fff5e7e7e4e0edd4f3f9f5fdf8baf7fbf9">[email protected]</a>. Will be writing in a few days. Thanks
if anyone has contributor access, can you send please dumps to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="fd9ea29a888d89bd849c959292d39e9290">[email protected]</a>
"If enabled, the default instance of the SQL Server Database Engine listens on TCP port 1433." https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port?view=sql-server-ver16
If anyone has contributor access... Can u please mail the dumps to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="caa0a5a2a4b9a5a4aea3baa5ff8aada7aba3a6e4a9a5a7">[email protected]</a>... It will be great help.