A global enterprise wants to bring their on-premises Windows and Linux servers and an existing Amazon EKS cluster under Azure governance for inventory, policy, and GitOps-based configuration. They will not move these resources to Azure. Which two actions should you perform?

The correct actions are to install the Azure Connected Machine agent on the servers and connect the EKS cluster using Azure Arc-enabled Kubernetes agents. The Azure Connected Machine agent allows on-premises Windows and Linux servers to be managed as Azure Arc-enabled servers, enabling Azure governance features like inventory and policy. Similarly, installing Azure Arc-enabled Kubernetes agents on the EKS cluster integrates it with Azure for management and GitOps-based configuration. Deploying only the Azure Monitor agent via Group Policy will not automatically onboard servers to Azure Arc; a separate agent is required for Arc. Creating an Azure Arc-enabled data services instance is for managing data services, not for automatically enrolling all non-Azure servers and clusters. Migrating servers to Azure Stack HCI is a migration strategy, not a method for extending Azure governance to existing non-Azure infrastructure, and Azure Arc does support non-Azure infrastructure.