AZ-204 Developing for Microsoft Azure Exam Prep - Access Keys and Shared Access Signatures

The video tutorial explains the concept of public endpoints in Geo redundant storage accounts, detailing the primary and secondary endpoints. It covers static website hosting in storage accounts, allowing HTML, CSS, and JavaScript uploads. The tutorial discusses access keys, their security risks, and how to use them programmatically. It also introduces Shared Access Signatures (SAS) for controlled access, explaining how to generate and use SAS tokens, and the limitations in revoking them.

What is the primary purpose of the secondary endpoint in a geo-redundant storage account?

• To provide read-only access

• To host static websites

• To provide write access

• To store backup data

Which of the following is NOT a component of a storage account?

• Databases

• Queues

• Blobs

• Tables

What is the main risk associated with sharing access keys?

• They provide full administrative access

• They expire quickly

• They are difficult to use

• They can be easily regenerated

How can a connection string be used in relation to a storage account?

• To regenerate access keys

• To connect programmatically

• To host a static website

• To list all public endpoints

What is a key advantage of using a shared access signature (SAS) over an access key?

• SAS is easier to remember

• SAS can be used without an internet connection

• SAS provides full access to the storage account

• SAS allows for specific permissions and expiration times

What must be done to invalidate a shared access signature (SAS) token?

• Edit the SAS token

• Regenerate the access key

• Change the storage account's URL

• Delete the storage account

Which of the following can be specified when creating a shared access signature (SAS)?

• The specific permissions granted

• The storage account's primary endpoint

• The storage account's backup frequency

• The storage account's location