Indexing Large OneDrive Files with Azure Video Indexer
You have a Microsoft OneDrive folder that contains a 20-GB video file named File1.avi. You need to index File1.avi by using the Azure Video Indexer website. What should you do?
Community Votes
54% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The core concept is integrating cloud storage with AI services via public URLs, while the common trap is assuming large file size limitations prevent URL-based indexing or that download links are the only option.
This question tests the method for indexing large media files stored in OneDrive using Azure AI Video Indexer. The correct approach involves creating a sharing link to provide direct access without local re-uploading.
Many candidates choose Option B (download and upload) because they incorrectly assume the 2-GB limit applies to all indexing methods or distrust URL access for large files, ignoring that Video Indexer supports larger files via direct URL.
Community Discussion (25 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D is the correct action because Azure AI Video Indexer accepts video URLs from various sources, including OneDrive. By creating a sharing link in OneDrive, you generate a public URL that the indexer can fetch directly. This avoids the inefficiency of downloading and re-uploading a massive 20-GB file, which would be prone to timeout failures and bandwidth waste.Why the Other Options Are Wrong
Option A is incorrect because Azure AI Video Indexer explicitly blocks URLs from streaming platforms like YouTube to prevent copyright and technical conflicts. Option B is impractical for a 20-GB file; downloading such a large asset locally and then uploading it to the service is inefficient and likely to fail due to time limits or network instability. Option C is technically flawed because OneDrive's native 'Download' link behavior often triggers a browser download rather than providing a raw streamable URL suitable for API ingestion, whereas a Sharing Link provides the necessary direct access endpoint.Community Comment Notes
Community discussion highlights the confusion around file size limits and link types. User cited documentation suggesting a 2 GB limit but failed to account for exceptions or newer capabilities allowing larger files via URL. User suggested hacking embed codes into download links, which is overly complex and unstable compared to standard sharing features. User correctly identified that sharing links provide the required public access without authentication hurdles, aligning with official best practices for integration.Official Reference
Exam Strategy
When dealing with large files in cloud exams, always look for solutions that minimize data movement. If an AI service accepts URLs, prefer linking over downloading/re-uploading, unless specific security constraints (like private VNETs) are mentioned.
Frequently Asked Questions
Why can't I use a YouTube URL for Azure Video Indexer?
Azure AI Video Indexer does not support indexing videos from third-party streaming services like YouTube due to policy restrictions and technical incompatibilities.
Is there a file size limit for URL-based indexing?
While older documentation cited a 2 GB limit, modern implementations support larger files via direct URLs. However, extremely large files may still face timeouts, making efficient linking crucial.