You have deleted the QnA Maker service in Azure.
With the next billing cycle, you did not expect to see the associated costs to show.
However, to your surprise, you see some amount showed up.
Your application is using a custom domain and autoscaling features.
You are using more than fifteen indexes per service.
You have been storing the state in memory.
You work with Microsoft contact and conclude that some of the associated services will continue to accrue the cost until you delete them.
Which two services would you choose to delete to avoid additional costs in the subsequent billing cycles?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answers: B and D.
Option A is incorrect because Azure table storage would be used if you design and implement it to store the state in the table storage.
In the scenario above, the state is stored in memory.
Option B is correct.
While you create QnA maker service, Azure Cognitive Search service is also created.
Since you are using more than fifteen indexes per service, you would be using a Standard tier.
Unless you delete the Cognitive Search resource, you will continue to incur costs.
Option C is incorrect.
Azure resource group is a container that holds resources for your solution.
It does not have a cost associated with it.
Option D is correct.
Azure App Service that uses autoscaling requires a Standard tier, and hence you would continue to incur costs if you do not delete it.
Reference:
To learn more about costs associated with cognitive resources, use the link given below:
Based on the scenario described, you have deleted the QnA Maker service but still see some costs in your billing. The reason behind this is that some associated services are still running and accumulating charges.
To avoid additional costs in the subsequent billing cycle, you need to identify which services you can delete.
Out of the four options provided, you should consider deleting Azure Table Storage and Azure Cognitive Search.
Here's why:
Azure Table Storage is a NoSQL key-value store that allows you to store large amounts of unstructured data. It is a good option for storing non-relational data and is often used by applications that require fast access to data. However, in this scenario, it's possible that you're not using Table Storage to store any data related to your application. Therefore, it makes sense to delete it to avoid incurring unnecessary costs.
Azure Cognitive Search is a search-as-a-service offering that allows you to add search capabilities to your applications. It's possible that you're using Azure Cognitive Search to search through your QnA Maker service, but since you've deleted the QnA Maker service, you may not need the search capabilities provided by Cognitive Search anymore. Therefore, you can choose to delete it as well.
Azure Resource Group is a logical container for resources deployed to Azure. Deleting the resource group would delete all resources that are part of it. However, it's not clear from the scenario if you have any other resources in this resource group that you need to keep, so it's not a safe option to delete it.
Azure App Service is a fully managed platform for building, deploying, and scaling web apps. The scenario mentions that you are using custom domain and autoscaling features, which indicates that you're likely using App Service to host your application. Therefore, deleting App Service would make your application unavailable, and it's not a recommended option.
In summary, you should consider deleting Azure Table Storage and Azure Cognitive Search to avoid additional costs in the subsequent billing cycle.