A user needs to configure NGC CLI to access resources across multiple organizations.

The correct answer is ngc config set --org org-name --ace ace-name. NGC CLI uses configuration context to determine which organization, team, or entitlement scope the user is operating in. When users belong to multiple organizations, the CLI must be configured with the intended organization context so that registry access, model downloads, private containers, and enterprise software resources resolve correctly. NVIDIA documentation shows ngc config set as the command used to configure or switch NGC context, including organization and team values, and other NVIDIA installation workflows show NGC configuration prompting for organization, team, and ACE fields. Manually editing JSON configuration files is not the recommended operational method because it increases the risk of syntax errors and inconsistent authentication state. ngc registry login is not the normal command for setting persistent NGC CLI organization context. Exporting an environment variable may influence a session, but it is not the best persistent configuration method. In AI infrastructure operations, correct NGC configuration is important for pulling validated containers, GPU drivers, vGPU software, models, and enterprise assets from the correct account scope.