HP HPE6-A90 Exam
HPE Networking Central Exam
https://www.passquestion.com/hpe6-a90.html
35% OFF on All, Including HPE6-A90 Questions and Answers
Pass HPE6-A90 Exam with PassQuestion HPE6-A90 questions and
answers in the first attempt.
https://www.passquestion.com/
1/6
, 1.A Central Platform Administrator is automating the migration of a massive enterprise network. They
must dynamically assign 5,000 newly onboarded AOS-CX switches into specific Configuration Groups
based on their role, and apply appropriate Device Tags for monitoring.
The enterprise utilizes a multi-tenant architecture with two distinct GreenLake Workspaces:
Workspace_Corp and Workspace_Retail.
The administrator executes a bulk API script to apply the tag [Status: Pre-Prod] and assign the switches to
the Grp_Access_Baseline Configuration Group.
API Response Snippet:
{
"success": 2450,
"failed": 2550,
"errors": [
{
"device_mac": "00:1A:2B:3C:4D:5E",
"error": "Group Grp_Access_Baseline not found in current context."
},
{
"device_mac": "00:1A:2B:3C:4D:5F",
"error": "Tag assignment failed: Device belongs to a different tenant workspace."
}
]
}
Based on the interaction between Workspace boundaries, Configuration Groups, and Tagging mechanics,
which THREE statements explain these API failures? (Select all that apply.)
A. Devices must be fully licensed and assigned to a Configuration Group BEFORE any Device Tags can
be applied to them via the Central API.
B. Configuration Groups are strictly bounded within a single Workspace. A group named
Grp_Access_Baseline created in Workspace_Corp does not exist and cannot be referenced by devices in
Workspace_Retail.
C. Device Tags are global entities within GreenLake; however, the API token used was scoped strictly to
Workspace_Corp, preventing tag application on devices residing in Workspace_Retail.
D. True multi-tenant automation requires executing the group assignment and tagging API calls
independently against the specific API Gateway endpoint corresponding to each distinct Workspace.
E. The API script failed because it attempted to assign a tag ([Status: Pre-Prod]) that contains special
characters (brackets and hyphens), which violates Central's tag naming conventions.
Answer: B, C, D
2.An enterprise deploys AOS-10 Campus APs that tunnel traffic to a centralized Gateway cluster. The
campus network enforces strict Zero Trust using 802.1X port-based security on all wired AOS-CX access
switches. The APs must cryptographically authenticate to the switch port before gaining uplink access to
the network.
[AOS-CX Switch - Port Access Configuration]
interface 1/1/5
port-access dot1x enable
2/6
HPE Networking Central Exam
https://www.passquestion.com/hpe6-a90.html
35% OFF on All, Including HPE6-A90 Questions and Answers
Pass HPE6-A90 Exam with PassQuestion HPE6-A90 questions and
answers in the first attempt.
https://www.passquestion.com/
1/6
, 1.A Central Platform Administrator is automating the migration of a massive enterprise network. They
must dynamically assign 5,000 newly onboarded AOS-CX switches into specific Configuration Groups
based on their role, and apply appropriate Device Tags for monitoring.
The enterprise utilizes a multi-tenant architecture with two distinct GreenLake Workspaces:
Workspace_Corp and Workspace_Retail.
The administrator executes a bulk API script to apply the tag [Status: Pre-Prod] and assign the switches to
the Grp_Access_Baseline Configuration Group.
API Response Snippet:
{
"success": 2450,
"failed": 2550,
"errors": [
{
"device_mac": "00:1A:2B:3C:4D:5E",
"error": "Group Grp_Access_Baseline not found in current context."
},
{
"device_mac": "00:1A:2B:3C:4D:5F",
"error": "Tag assignment failed: Device belongs to a different tenant workspace."
}
]
}
Based on the interaction between Workspace boundaries, Configuration Groups, and Tagging mechanics,
which THREE statements explain these API failures? (Select all that apply.)
A. Devices must be fully licensed and assigned to a Configuration Group BEFORE any Device Tags can
be applied to them via the Central API.
B. Configuration Groups are strictly bounded within a single Workspace. A group named
Grp_Access_Baseline created in Workspace_Corp does not exist and cannot be referenced by devices in
Workspace_Retail.
C. Device Tags are global entities within GreenLake; however, the API token used was scoped strictly to
Workspace_Corp, preventing tag application on devices residing in Workspace_Retail.
D. True multi-tenant automation requires executing the group assignment and tagging API calls
independently against the specific API Gateway endpoint corresponding to each distinct Workspace.
E. The API script failed because it attempted to assign a tag ([Status: Pre-Prod]) that contains special
characters (brackets and hyphens), which violates Central's tag naming conventions.
Answer: B, C, D
2.An enterprise deploys AOS-10 Campus APs that tunnel traffic to a centralized Gateway cluster. The
campus network enforces strict Zero Trust using 802.1X port-based security on all wired AOS-CX access
switches. The APs must cryptographically authenticate to the switch port before gaining uplink access to
the network.
[AOS-CX Switch - Port Access Configuration]
interface 1/1/5
port-access dot1x enable
2/6
