The correct option is Use the REST API endpoints to list current Copilot seat assignments and to grant or revoke seats for organization members and outside collaborators.

GitHub Copilot for Business provides REST endpoints that let organization administrators list current seat assignments and grant or revoke seats for members and outside collaborators. This enables reliable automation for onboarding and offboarding because you can read the current state and then assign or remove seats in response to your identity or access changes.

Use the REST API to automatically convert Copilot Individual licenses in user accounts into Copilot Business seats across the organization is incorrect because there is no API to convert personal Copilot Individual subscriptions into organization seats. Individual and organization subscriptions are managed separately and organization admins assign Business seats without converting personal plans through the API.

Configure the REST API to issue invitations and to automatically assign Copilot seats whenever a new member is added to the organization without any external workflow is incorrect because the REST API does not self trigger actions. You would need an external workflow such as webhooks and automation to react to membership changes and then call the seat management endpoints. While you can invite users and then assign seats, automation requires an orchestrator outside the API itself.

Cloud Billing API is incorrect because it is unrelated to GitHub and does not manage GitHub Copilot Business subscriptions or seats.

Full AWS Practitioner Certification Question