Scenario Recap:
* Goal: Ensure app1 (on VM1 in vnet1) can connect to service1 (Azure Cognitive Search) without routing over the public internet.
* Proposed Solution: Deploy service1 with a public endpoint, and configure an IP firewall rule.
Analysis:
* IP firewall rules restrict which public IPs can access a service.
* However, traffic still routes over the public internet. The firewall only filters access, it does not provide private connectivity.
* To avoid internet traffic, you must use Private Link (private endpoint).
The answer: B. No
Reference: Secure access to Cognitive Search with Private Link

You have files with the following formats:
File1: WMV (34 mins, 400 MB)
File2: AVI (90 mins, 1,200 MB)
File3: MOV (300 mins, 980 MB)
File4: MP4 (80 mins, 1,800 MB)
You must determine which files can be uploaded to Azure AI Video Indexer.
Key Rules (Video Indexer upload limitations):
Supported formats: MP4, MOV, WMV, AVI, M2TS.
Maximum file length: 4 hours (240 minutes).
Maximum file size: 2 GB (2048 MB) for website uploads.
Check each file:
File1 (WMV, 34 min, 400 MB): Supported format, within time and size # # Allowed.
File2 (AVI, 90 min, 1,200 MB): Supported format, within time and size # # Allowed.
File3 (MOV, 300 min, 980 MB): Supported format, but exceeds 240 min limit # # Not Allowed.
File4 (MP4, 80 min, 1,800 MB): Supported format, within size (under 2 GB), within time # # Allowed.
The Answer:
A). File1, File2, and File4 only
Microsoft Reference:
Video Indexer upload limitations

For Azure AI Agent Service, the documented quota for the maximum total size of all files uploaded for agents has been listed as 100 GB. Individual files are limited to 512 MB each. These limits are relevant when you plan an agent that must combine and process multiple user-uploaded files.
(Note: Quotas can evolve; check the current "Quotas and limits" page for your region.) References (Microsoft Docs / Q & A):
Microsoft Q & A (Agent Service limits: "Max size for all uploaded files for agents 100 GB"; per-file 512 MB). Microsoft Learn File Search tool how-to (per-file 512 MB guidance). Microsoft Learn

* A streaming workload means data is generated continuously and ingested in near real time.
* Telemetry from edge/IoT devices is a classic example of streaming workloads because the devices constantly push data (sensor readings, logs, metrics).
* A. sending transactions daily # batch workload (not streaming).
* B. sending metadata every 30 minutes # periodic batch, not continuous streaming.
* C. sending old transactions to archive # cold data archival, not streaming.
The answer: D
Reference: Azure Stream Analytics overview