Exam AZ-104 topic 1 question 28 discussion

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, 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.

B is correct You enable Floating IP.

B is corerct

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.

Port 1433 for database connections pool, not for HTTP protocol in health check.

"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

No is correct answer,as Port 1433 for TCP is needed to connect to the SQL database instance

Port 1433 for TCP is needed to connect to the SQL database instance 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

Option B is correct

B. No. The solution mentioned in the scenario is not correct. Creating an HTTP health probe on port 1433 will not work because SQL Server does not use HTTP as a protocol. The HTTP health probe will not be able to determine if the SQL Server instance is running or not. 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 as a protocol, and a TCP health probe will be able to determine if the SQL Server instance is running or not. Therefore, the correct solution is to create a TCP health probe on port 1433.

yes. port 1433 health probe should monitor the status of microsoft sql server. if this port is healthy, it means the app running on the server, the connection to db, as well as the VM itself are all healthy. In fact this is the best practice whenever possible since it can monitor at the app/db level not just the VM level.

"An availability group listener is a virtual network name that clients connect to for database access. On Azure Virtual Machines in a single subnet, a load balancer holds the IP address for the listener." To configure an Azure internal load balancer as a listener for the availability group you need to configure an "availability group listener" not a HTTP health probe

Eliminate the need for an Azure Load Balancer for your Always On availability (AG) group by creating your SQL Server VMs in multiple subnets within the same Azure virtual network.

1433 is a sql port, http is 80, so NO.

Health probe to check if backend vm is healthy.