Home » Microsoft » 70-532 v.2 » Which three actions should you perform in sequence?
DRAG DROP
You need to ensure that the drug dosage endpoint is always resolved and accessible.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
Select and Place:
Correct Answer:
Explanation/Reference:
Explanation:
Step 1: The reverse proxy addresses services in the cluster that exposes HTTP endpoints including HTTPS. The reverse proxy greatly simplifies calling other services and their methods by having a specific URI format and handles the resolve, connect, retry steps required for one service to communicate with another using the Naming Service. In other words, it hides the Naming Service from you when calling other services by making this as simple as calling a URL.
You can use the Azure Resource Manager template to enable the reverse proxy in Service Fabric for the cluster.
Step 2: Instead of configuring the port of an individual service in Load Balancer, you can configure just the port of the reverse proxy in Load Balancer. This configuration lets clients outside the cluster reach services inside the cluster by using the reverse proxy without additional configuration.
Scenario: You develop a drug pricing endpoint as an Azure App Service API app. The drug pricing endpoint requires API discovery that uses the Swagger RESTful API Documentation Specification (also known as the OpenAPI specification). Developers would like to generate operation identifiers for overloads of their controller methods. In addition, developers are finding it difficult to secure the API endpoints by using authentication and authorization to restrict access to certain resources within the app without writing extra, custom code.
You develop a drug dosage endpoint as a Service Fabric, OWIN-hosted, HTTPS endpoint. Developers are having difficulty writing and maintaining code to wrap client-side communication libraries in a retry loop for situations when the endpoints are down.
DevOps have extensive experience with PowerShell and would like to maintain Azure resources by using Azure PowerShell.