You develop an app that allows users to upload photos and videos to Azure storage. The app uses a storage REST API call to upload the media to a blob storage account named Account1. You have blob storage containers named Container1 and Container2.
Uploading of videos occurs on an irregular basis.
You need to copy specific blobs from Container1 to Container2 in real time when specific requirements are met, excluding backup blob copies.
What should you do?
To copy specific blobs in real time from Container1 to Container2, you should use the Put Blob operation of the Blob Service REST API. This approach allows for programmatic control and immediate copying of blobs upon meeting specific requirements. Using the REST API ensures that the operation can be integrated directly into your application's existing upload process, maintaining real-time performance. While other methods such as PowerShell commands can start a copy operation, they do not inherently guarantee real-time execution as effectively as directly using the REST API for blob operations.
why not C? The REST API for uploading is already supported. Also, coping with PowerShell or CLI seems not to be good choices for "real time" requirement.
I tend to agree with you. Now if B said something like create a PS runbook that is set on a webhook connected to storage account then that would make sense.
I think it's C too. As it uses storage REST API to upload to Container1, it's easy to do the same to put into Container2 at the same time to make it ' in real time'
Copy with Put Blob (C) requires more step, for example, Put Blob on page blob and append blob only initialize the blob, additional step is needed to copy the blob. So i think the answers is B. https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob
B doesn't meet the 'real-time' requirement. It has to be done by code.
It uses a storage REST API to upload media, so the block type is a Block Blob, not a Page Blob (used for VM) and Append Blob (used to append data like logs) So I think the correct answer is C. For a block blob, the request body contains the content of the blob (see https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob#request-body)
Anyone saying put, The Put Blob operation creates a new block, page, or append blob, or updates the content of an existing block blob. Answer is B because you want to copy in realtime even if it is ps script.
Answer should be C B only makes sense if it was "Create a PS script and set it up by AZ Functions or Webjobs", but it's "Run PS ..." which means triggered manually and couldn't meet the "real time" requirement
If Start-AzureStorageBlobCopy is triggered by Event Grid then it make sense, which is not mentioned here so C is correct. For following question, since Event Grid is mentioned with Start-AzureStorageBlobCopy, that make sense: https://www.examtopics.com/discussions/microsoft/view/37714-exam-az-204-topic-3-question-24-discussion/
There is a similar question in az204: https://www.examtopics.com/discussions/microsoft/view/37714-exam-az-204-topic-3-question-7-discussion/ In both the option C is available. So in choice between B and C, I would go with C
Sorry, my fault. This are different questions....
The Put Blob operation creates a new block, page, or append blob, or updates the content of an existing block blob. Updating an existing block blob overwrites any existing metadata on the blob. The difference between the two is likely AzCopy is operating a bulk mode and Start-AzureStorageBlobCopy is operating serially due to piping the blobs in one by one, sending request to initiate the transfer