Epoch Analytics needs to enable NSG Flow Logs v2 for several subscription VNets and ingest logs into a central Log Analytics workspace for Traffic Analytics. Which sequence of actions and configuration is required to enable Flow Logs v2 and Traffic Analytics correctly?

The correct approach involves enabling Flow Logs v2 directly on each Network Security Group (NSG) that needs monitoring. When enabling, you specify the central Log Analytics workspace as the destination, providing its resource ID and region. After Flow Logs are configured, you then enable Traffic Analytics within that Log Analytics workspace by linking the Traffic Analytics solution. This ensures that the flow data is collected and processed for network traffic insights. The other options are incorrect because: Enabling NSG Flow Logs at the subscription level is not a standard or supported method for configuring Flow Logs. Flow Logs are typically configured per NSG or per VNet. Azure Monitor Network Insights provides network health and performance monitoring but does not automatically route NSG Flow Logs to a storage account or configure Traffic Analytics with Azure Sentinel. Diagnostic Settings on NSGs are for sending metrics and activity logs, not for NSG Flow Logs, which are a distinct feature. Using Event Hubs and custom parsers for Flow Logs is an overly complex and incorrect method when direct integration with Log Analytics and Traffic Analytics is available.