Practice Exam

Explanations for each answer:

• Update the retail store location data upload process to include blob index tags. Create an Azure Function to process the blob index tags and filter by store location is incorrect. While blob index tags can categorize transactions by store location, they're designed for discovery and filtering of existing blobs, not for auditing changes. Index tags don't capture transaction events (create, update, delete) or provide an audit trail of when changes occurred. For auditing sales transactions, you need event-driven or change log approaches that capture temporal information.
• Enable blob versioning for the storage account. Use an Azure Function to process a list of the blob versions per day is incorrect. Blob versioning creates immutable snapshots when blobs are overwritten, preserving historical states for compliance and recovery. However, versioning doesn't provide event notifications or timestamps for when changes occurred, making it inefficient for real-time auditing. You'd need to manually enumerate and compare versions to determine what changed and when, which doesn't meet audit trail requirements.
• Process an Azure Storage blob inventory report by using an Azure Function. Create rule filters on the blob inventory report is incorrect. Blob inventory generates scheduled reports (daily or weekly) listing blobs and their properties for compliance and cost management. However, inventory reports are snapshots taken at specific intervals, not continuous audit logs. They don't capture individual transaction events or provide the temporal granularity needed for auditing sales transactions as they occur throughout the day.
• Subscribe to blob storage events by using an Azure Function and Azure Event Grid. Filter the events by store location is correct. Event Grid provides real-time event notifications when blobs are created, modified, or deleted, enabling immediate auditing of sales transaction uploads. You can create an Event Grid subscription that triggers an Azure Function for blob events, filtering by store location using subject filters or custom properties. This provides a comprehensive, real-time audit trail with timestamps and event details for each transaction.
• Process the change feed logs of the Azure Blob storage account by using an Azure Function. Specify a time range for the change feed data is correct. Change feed provides ordered, immutable, read-only transaction logs of all create, modify, and delete operations on blobs and metadata. It captures complete audit information including timestamps and operation types, making it ideal for compliance and auditing. An Azure Function can process change feed logs within specific time ranges to audit sales transactions by store location, providing a durable and complete audit trail.