Summary, clean up and knowledge check

Completed

Summary

Congratulations!

In this module, you learned how to use Azure Blob Storage to store web app data. You followed these steps:

1. You discovered tips for creating a strategy to use Blob Storage in a web app.

2. You learned how to use the Azure Storage SDK to list, write to, and read from blobs.

3. You created an app that accepts uploaded files from users, stores them in Blob Storage, and makes them available for download.

4. You deployed the app to Azure App Service.

Further Reading

• Index data from Azure Blob Storage
• Naming and Referencing Containers, Blobs, and Metadata
• Security recommendations for Blob storage
• Configure an ASP.NET Core app for Azure App Service
• Deploy and configure a Tomcat, JBoss, or Java SE app in Azure App Service

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources that you leave running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Check your knowledge

1.

Which of the following describes a good strategy for creating storage accounts and blob containers for your application?

Create both your Azure Storage accounts and containers before deploying your application.

Create Azure Storage accounts in your application as needed. Create the containers before deploying the application.

Create Azure Storage accounts before deploying your app. Create containers in your application as needed.

2.

Which of the following can be used to initialize the Blob Storage client library within an application?

An Azure username and password.

The Azure Storage account connection string.

A globally unique identifier (GUID) that represents the application.

The Azure Storage account datacenter and location identifiers.

3.

What happens when you obtain a BlobClient reference from BlobContainerClient with the name of a blob?

A new block blob is created in storage.

A BlobClient object is created locally. No network calls are made.

An exception is thrown if the blob does not exist in storage.

The contents of the named blob are downloaded.

You must answer all questions before checking your work.