AZ-305 Design business continuity solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Step 1: Obtain a TLS/SSL certificate. Step 2: Upload the certificate to the Application Gateway. Step 3: Configure the backend pool. Step 4: Create backend HTTP settings with HTTPS and upload the backend certificate (if required). Step 5: Create a routing rule.

  Why this is correct

  The correct sequence begins with obtaining a TLS/SSL certificate because the front-end listener cannot terminate HTTPS without a certificate. Uploading it to the Application Gateway makes the certificate available for listener configuration. The backend pool is this established to define the target servers, and the backend HTTP settings then specify the protocol and optionally the trusted backend certificate. Finally, the routing rule is created to connect the listener to the pool using those settings, which is why this dependency-driven order is correct.

• ✗

  Step 1: Upload the certificate to the Application Gateway. Step 2: Obtain a TLS/SSL certificate. Step 3: Configure the backend pool. Step 4: Create backend HTTP settings with HTTPS and upload the backend certificate. Step 5: Create a routing rule.

  Why it's wrong here

  This sequence invalidly places the certificate upload before its acquisition. In Azure, you must first obtain a certificate—either from a public CA or as a self-signed PFX—before you can import it into the Application Gateway; trying to upload a non-existent certificate will fail. Consequently, this order cannot be executed and must be corrected by moving the 'Obtain' step first.

• ✗

  Step 1: Obtain a TLS/SSL certificate. Step 2: Configure the backend pool. Step 3: Upload the certificate to the Application Gateway. Step 4: Create backend HTTP settings with HTTPS and upload the backend certificate. Step 5: Create a routing rule.

  Why it's wrong here

  Uploading the certificate should be done before configuring backend HTTP settings that reference it. Also, the backend pool can be configured any time after the certificate is obtained, but it is typically done after upload.

• ✗

  Step 1: Obtain a TLS/SSL certificate. Step 2: Upload the certificate to the Application Gateway. Step 3: Create backend HTTP settings with HTTPS and upload the backend certificate. Step 4: Configure the backend pool. Step 5: Create a routing rule.

  Why it's wrong here

  After the certificate is obtained and uploaded, the backend pool should be configured before the backend HTTP settings, because those settings are written to be associated with a pool in the routing rule. Creating the HTTP settings first leaves them without a pool to reference, and the portal workflow and rule creation require the pool to exist. Thus this order, which swaps steps 3 and 4, will cause a misconfiguration or force a redo.

Go deeper

Related to this question