NVIDIA NCP-AII Practice Test 50
Question 490
During an NVIDIA AI factory acceptance test, engineers discover: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. Which TWO complementary elements are needed: the correct technical action and the strongest independent diagnostic evidence? Select TWO answers.
- Check HA roles, sync status, virtual management endpoint, database replication and isolation tests.
- Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel.
- Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout.
- Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery.
- Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests.
Explanation
Correct Answers
C:This is an appropriate correction for Linux operating system and kernel module support: Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. The governing mechanism is: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
E:This is the direct operational evidence to investigate: Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
Incorrect Answers
A:This alternative is relevant to BCM high availability and management failover but does not directly resolve the current Linux operating system and kernel module support issue: Check HA roles, sync status, virtual management endpoint, database replication and isolation tests. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
B:This tempting but unsafe shortcut is not a sufficient remediation for Linux operating system and kernel module support: Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel. A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
D:This alternative is relevant to Host SSH certificates keys and OS access segregation but does not directly resolve the current Linux operating system and kernel module support issue: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
Question 491
A production GPU cluster review identifies this condition: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Review slurm.conf, controller health, partition listings, node state and a submitted sample job.
- Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel.
- Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests.
- Inspect DHCP leases, PXE requests, image revisions, BCM node mappings and host boot traces.
Explanation
Correct Answer
C:This is the direct operational evidence to investigate: Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. The governing mechanism is: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
Incorrect Answers
A:This alternative is relevant to Slurm controller partition setup but does not directly resolve the current Linux operating system and kernel module support issue: Review slurm.conf, controller health, partition listings, node state and a submitted sample job. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
B:This tempting but unsafe shortcut is not a sufficient remediation for Linux operating system and kernel module support: Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. The governing mechanism is: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness. The proportionate action is: Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout.
D:This alternative is relevant to BCM image provisioning and PXE worker boot but does not directly resolve the current Linux operating system and kernel module support issue: Inspect DHCP leases, PXE requests, image revisions, BCM node mappings and host boot traces. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
Question 492
In a professional AI infrastructure deployment, a technician observes: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel.
- New and restarted nodes load the intended GPU and fabric drivers and pass required cluster smoke tests.
- Each workload reaches the intended high-speed path and RDMA transfer passes with correct device selection.
- The management node reports correct cluster state and consistently deploys an approved image to intended nodes.
Explanation
Correct Answer
B:This is an observable verified result, not merely a claimed configuration change: New and restarted nodes load the intended GPU and fabric drivers and pass required cluster smoke tests. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
Incorrect Answers
A:This tempting but unsafe shortcut is not a sufficient remediation for Linux operating system and kernel module support: Equate package installation success with a working signed GPU driver for any arbitrary Linux kernel. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary. The governing mechanism is: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness. The proportionate action is: Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout. A direct check is: Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests. The acceptance condition is: New and restarted nodes load the intended GPU and fabric drivers and pass required cluster smoke tests.
C:That option concerns Compute fabric interface bonding and RDMA prerequisites. Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
D:This alternative is relevant to Base Command Manager head-node installation but does not directly resolve the current Linux operating system and kernel module support issue: The management node reports correct cluster state and consistently deploys an approved image to intended nodes. Observed scenario: A security team forces an emergency kernel update without testing network RDMA and GPU support on a canary.
Question 493
The cluster operations team needs to evaluate this situation: All data center workers share one root SSH password and failed-login events cannot be attributed to operators. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout.
- Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery.
- Define explicit BCM node categories and managed overrides for shared hardware and service configuration.
Explanation
Correct Answer
C:This is an appropriate correction for Host SSH certificates keys and OS access segregation: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Incorrect Answers
A:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
B:This alternative is relevant to Linux operating system and kernel module support but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Use the supported OS, kernel and package combination and validate driver modules on a representative node before rollout. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
D:This alternative is relevant to BCM node categories and role inheritance but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Define explicit BCM node categories and managed overrides for shared hardware and service configuration. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Question 494
At a multi-node AI infrastructure handoff, the team records: All data center workers share one root SSH password and failed-login events cannot be attributed to operators. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
- Cluster managers coordinate images, nodes, services and configuration; worker OS boot cannot replace control-plane readiness.
- Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
Explanation
Correct Answer
C:This is the governing infrastructure principle: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Incorrect Answers
A:This alternative is relevant to Linux operating system and kernel module support but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
B:That option concerns Base Command Manager head-node installation. The acceptance condition is: Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events.
D:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
Question 495
During an NVIDIA AI factory acceptance test, engineers discover: All data center workers share one root SSH password and failed-login events cannot be attributed to operators. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect category membership, inherited images, node overrides, resulting configuration and change impact.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- Inspect BCM service health, database backups, node discovery, management interfaces and provisioning records.
- Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs.
Explanation
Correct Answer
D:This is the direct operational evidence to investigate: Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Incorrect Answers
A:This alternative is relevant to BCM node categories and role inheritance but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Inspect category membership, inherited images, node overrides, resulting configuration and change impact. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
B:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
C:This alternative is relevant to Base Command Manager head-node installation but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Inspect BCM service health, database backups, node discovery, management interfaces and provisioning records. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Question 496
A production GPU cluster review identifies this condition: All data center workers share one root SSH password and failed-login events cannot be attributed to operators. After corrective work, which observable result BEST confirms that the requirement is met? Select ONE best answer.
- Approved users run permitted jobs and view only their data, while revoked identities cannot access compute or artifacts.
- Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- The management node reports correct cluster state and consistently deploys an approved image to intended nodes.
Explanation
Correct Answer
B:This is an observable verified result, not merely a claimed configuration change: Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Incorrect Answers
A:This alternative is relevant to Cluster user identities quota and access management but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Approved users run permitted jobs and view only their data, while revoked identities cannot access compute or artifacts. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
C:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. All data center workers share one root SSH password and failed-login events cannot be attributed to operators. Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
D:This alternative is relevant to Base Command Manager head-node installation but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: The management node reports correct cluster state and consistently deploys an approved image to intended nodes. Observed scenario: All data center workers share one root SSH password and failed-login events cannot be attributed to operators.
Question 497
In a professional AI infrastructure deployment, a technician observes: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. Which operational response is MOST appropriate to address the root issue? Select ONE best answer.
- Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- Validate DHCP/PXE services, provisioned image and node identity mapping, then test clean node reboots.
- Align supported interface or bond configuration, RDMA stack and fabric QoS with the cluster topology.
Explanation
Correct Answer
A:This is an appropriate correction for Host SSH certificates keys and OS access segregation: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Incorrect Answers
B:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
C:That option concerns BCM image provisioning and PXE worker boot. Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
D:This alternative is relevant to Compute fabric interface bonding and RDMA prerequisites but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Align supported interface or bond configuration, RDMA stack and fabric QoS with the cluster topology. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Question 498
The cluster operations team needs to evaluate this situation: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. Which underlying infrastructure principle BEST explains the issue? Select ONE best answer.
- Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
- A BCM category groups settings applied to member nodes; untracked manual changes may conflict with managed desired state.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness.
Explanation
Correct Answer
A:This is the governing infrastructure principle: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Incorrect Answers
B:That option concerns BCM node categories and role inheritance. The acceptance condition is: Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events.
C:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
D:This alternative is relevant to Linux operating system and kernel module support but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Accelerator and fabric software are kernel-dependent; a generic successful Linux boot does not establish full GPU readiness. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Question 499
At a multi-node AI infrastructure handoff, the team records: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. Which diagnostic evidence should be obtained FIRST to substantiate the likely fault or configuration gap? Select ONE best answer.
- Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
- Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs.
- Review slurm.conf, controller health, partition listings, node state and a submitted sample job.
Explanation
Correct Answer
C:This is the direct operational evidence to investigate: Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Incorrect Answers
A:This alternative is relevant to Linux operating system and kernel module support but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Inspect kernel version, signed modules, driver logs, package provenance and canary compatibility tests. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
B:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. The governing mechanism is: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions. The proportionate action is: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery.
D:This alternative is relevant to Slurm controller partition setup but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Review slurm.conf, controller health, partition listings, node state and a submitted sample job. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
Question 500
During an NVIDIA AI factory acceptance test, engineers discover: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. Which THREE elements together establish the appropriate corrective action, independent test evidence and verified successful outcome? Select THREE answers.
- Check HA roles, sync status, virtual management endpoint, database replication and isolation tests.
- Align supported interface or bond configuration, RDMA stack and fabric QoS with the cluster topology.
- Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs.
- Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events.
- Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery.
- Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster.
Explanation
Correct Answers
C:This is the direct operational evidence to investigate: Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. The governing mechanism is: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
D:This is an observable verified result, not merely a claimed configuration change: Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
E:This is an appropriate correction for Host SSH certificates keys and OS access segregation: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. The governing mechanism is: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
Incorrect Answers
A:This alternative is relevant to BCM high availability and management failover but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Check HA roles, sync status, virtual management endpoint, database replication and isolation tests. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic.
B:This alternative is relevant to Compute fabric interface bonding and RDMA prerequisites but does not directly resolve the current Host SSH certificates keys and OS access segregation issue: Align supported interface or bond configuration, RDMA stack and fabric QoS with the cluster topology. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. The governing mechanism is: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions.
F:This tempting but unsafe shortcut is not a sufficient remediation for Host SSH certificates keys and OS access segregation: Use one permanent shared root password on every compute node because workers belong to a trusted AI cluster. Observed scenario: A new GPU node exposes administrative SSH to a public test subnet intended only for application traffic. The governing mechanism is: Host administration requires least privilege and credential lifecycle control independently of GPU job permissions. The proportionate action is: Enforce individual authenticated host access, network restrictions and tested key rotation with accountable emergency recovery. A direct check is: Review authorized key and account policy, SSH server settings, firewall reachability and authentication logs. The acceptance condition is: Approved operators reach only assigned nodes and unauthorized sessions fail with traceable audit events.