You ingest high-throughput telemetry into an Azure Event Hub and must automatically archive all incoming events to long-term storage with minimal operational overhead. The archive should be written directly by the service without running custom code. What should you configure?

Event Hubs Capture is the correct solution because it directly archives all incoming events to a specified Azure Blob Storage or Azure Data Lake Storage Gen2 account with minimal operational overhead and without requiring custom code. It operates by capturing events in batches based on a configurable time or size window. Azure Stream Analytics (ASA) can achieve this but requires managing an ASA job, which adds operational overhead and involves writing a query, violating the "without running custom code" requirement. Event Hubs diagnostic settings export operational logs and metrics, not the actual event data. Event Grid subscriptions route events to various endpoints but don't inherently archive the full event stream to long-term storage in the desired format. There is no direct feature to configure a storage output directly from an Event Hubs namespace via a consumer group; consumer groups are for reading events, not archiving them.