Cisco 350-601 Practice Test 104
Question 1030
A network operations account can log in to NX-OS, yet its commands are denied because the server assigns an incorrect role. The observed failure is: a valid login alone does not prove the account has rights to apply a configuration change. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to use Fibre Channel zoning to grant user CLI permissions.
- The controlled remediation is to repair the mapped role or command rule and confirm only approved operations succeed.
- The controlled remediation is to give every technician the unrestricted network-admin role by default.
- The controlled remediation is to disable centralized AAA for all devices rather than checking the mapping.
Explanation
Correct Answer
B:This addresses the observable fault while preserving a check of the expected result. Validate against AAA method lists, TACACS+ server policy, returned role and command audit entries.
Incorrect Answers
A:Use Fibre Channel zoning to grant user CLI permissions. This would not reliably restore service after the stated fault. A valid login alone does not prove the account has rights to apply a configuration change. The controlled recovery is to repair the mapped role or command rule and confirm only approved operations succeed.
C:Give every technician the unrestricted network-admin role by default. This would not reliably restore service after the stated fault. A valid login alone does not prove the account has rights to apply a configuration change. The controlled recovery is to repair the mapped role or command rule and confirm only approved operations succeed.
D:Disable centralized AAA for all devices rather than checking the mapping. This would not reliably restore service after the stated fault. A valid login alone does not prove the account has rights to apply a configuration change. The controlled recovery is to repair the mapped role or command rule and confirm only approved operations succeed.
Question 1031
A read-only monitoring account unexpectedly has network-admin access after inheriting a broad role. Which next step should the data center engineer select?
- Rely on switch interface descriptions to enforce management privilege.
- Use one shared root credential for all users to simplify auditing.
- Apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
- Disable authorization checks when custom roles require review.
Explanation
Correct Answer
C:This directly addresses NX-OS local RBAC feature roles because rBAC limits administrative actions according to role rules and resource scope. Confirm the change against role definitions, assigned users, authorized command tests and accounting logs.
Incorrect Answers
A:Overbroad permissions undermine separation of duties and permit unauthorized changes. The relevant correction is to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
B:Use one shared root credential for all users to simplify auditing. The proposed change targets the wrong mechanism or lacks essential validation. RBAC limits administrative actions according to role rules and resource scope. Relevant evidence is role definitions, assigned users, authorized command tests and accounting logs.
D:Overbroad permissions undermine separation of duties and permit unauthorized changes. The appropriate action remains to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
Question 1032
A read-only monitoring account unexpectedly has network-admin access after inheriting a broad role. Which diagnostic record would most strongly confirm the result?
- A signed design diagram that lacks current access-policy or violation counters.
- An old role mapping that ignores the observed denial or unwanted permission.
- One successful management ping without validating the applicable policy.
- Role definitions, assigned users, authorized command tests and accounting logs.
Explanation
Correct Answer
D:These observations test the actual NX-OS local RBAC feature roles mechanism rather than a superficial management status. RBAC limits administrative actions according to role rules and resource scope.
Incorrect Answers
A:A signed design diagram that lacks current access-policy or violation counters. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
B:An old role mapping that ignores the observed denial or unwanted permission. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
C:One successful management ping without validating the applicable policy. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
Question 1033
A read-only monitoring account unexpectedly has network-admin access after inheriting a broad role. Which platform concept should guide the engineer’s assessment?
- RBAC limits administrative actions according to role rules and resource scope.
- A recognized device name establishes authentication and trust without checking keys.
- Physical connectivity makes all ACI contract and security policies optional.
- All traffic within a VLAN is necessarily authorized regardless of identity or policy.
Explanation
Correct Answer
A:This explains why the most appropriate response is to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests. Validation depends on role definitions, assigned users, authorized command tests and accounting logs.
Incorrect Answers
B:A recognized device name establishes authentication and trust without checking keys. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
C:Physical connectivity makes all ACI contract and security policies optional. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
D:All traffic within a VLAN is necessarily authorized regardless of identity or policy. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
Question 1034
A read-only monitoring account unexpectedly has network-admin access after inheriting a broad role. Assume an engineer instead chooses to rely on switch interface descriptions to enforce management privilege. Which root-cause observation follows from that incorrect change?
- Keeping valid key rotation records automatically disables the correct peer trust.
- Overbroad permissions undermine separation of duties and permit unauthorized changes.
- Reviewing an ACI contract causes the pre-existing permit rule to vanish.
- Testing one denied unauthorized connection proves the policy was absent.
Explanation
Correct Answer
B:The proper corrective action is to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests. RBAC limits administrative actions according to role rules and resource scope.
Incorrect Answers
A:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. The meaningful failure is that overbroad permissions undermine separation of duties and permit unauthorized changes.
C:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. The relevant evidence is role definitions, assigned users, authorized command tests and accounting logs.
D:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. In the given case, a read-only monitoring account unexpectedly has network-admin access after inheriting a broad role.
Question 1035
A read-only monitoring account unexpectedly has network-admin access after inheriting a broad role. The observed failure is: overbroad permissions undermine separation of duties and permit unauthorized changes. Which recovery action addresses the underlying technical fault?
- Use one shared root credential for all users to simplify auditing.
- Disable authorization checks when custom roles require review.
- Restrict the role, test permitted and denied commands, and verify session assignments.
- Rely on switch interface descriptions to enforce management privilege.
Explanation
Correct Answer
C:This addresses the observable fault while preserving a check of the expected result. RBAC limits administrative actions according to role rules and resource scope.
Incorrect Answers
A:Use one shared root credential for all users to simplify auditing. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.
B:Disable authorization checks when custom roles require review. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.
D:Rely on switch interface descriptions to enforce management privilege. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.
Question 1036
An infrastructure team creates a custom NX-OS role whose rule matches more commands than intended. What is the BEST supported implementation or corrective action?
- On this affected device, the engineer should use one shared root credential for all users to simplify auditing.
- On this affected device, the engineer should disable authorization checks when custom roles require review.
- On this affected device, the engineer should rely on switch interface descriptions to enforce management privilege.
- On this affected device, the engineer should apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
Explanation
Correct Answer
D:This directly addresses NX-OS local RBAC feature roles because rBAC limits administrative actions according to role rules and resource scope. In the given case, an infrastructure team creates a custom NX-OS role whose rule matches more commands than intended.
Incorrect Answers
A:Use one shared root credential for all users to simplify auditing. The proposed change targets the wrong mechanism or lacks essential validation. RBAC limits administrative actions according to role rules and resource scope. Relevant evidence is role definitions, assigned users, authorized command tests and accounting logs.
B:Overbroad permissions undermine separation of duties and permit unauthorized changes. In the given case, an infrastructure team creates a custom NX-OS role whose rule matches more commands than intended.
C:Overbroad permissions undermine separation of duties and permit unauthorized changes. Rely on switch interface descriptions to enforce management privilege.
Question 1037
An infrastructure team creates a custom NX-OS role whose rule matches more commands than intended. Which evidence BEST verifies the intended technical behavior?
- For this deployment, examine role definitions, assigned users, authorized command tests and accounting logs.
- For this deployment, examine a green link LED without confirming authentication, inspection or encryption state.
- For this deployment, examine a signed design diagram that lacks current access-policy or violation counters.
- For this deployment, examine an old role mapping that ignores the observed denial or unwanted permission.
Explanation
Correct Answer
A:These observations test the actual NX-OS local RBAC feature roles mechanism rather than a superficial management status. They should be checked after apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
Incorrect Answers
B:A green link LED without confirming authentication, inspection or encryption state. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
C:A signed design diagram that lacks current access-policy or violation counters. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
D:An old role mapping that ignores the observed denial or unwanted permission. This information cannot independently verify NX-OS local RBAC feature roles. The decisive records instead include role definitions, assigned users, authorized command tests and accounting logs. RBAC limits administrative actions according to role rules and resource scope.
Question 1038
An infrastructure team creates a custom NX-OS role whose rule matches more commands than intended. Which principle BEST explains why the recommended solution is appropriate?
- For this condition, the applicable principle is that all traffic within a VLAN is necessarily authorized regardless of identity or policy.
- For this condition, the applicable principle is that rBAC limits administrative actions according to role rules and resource scope.
- For this condition, the applicable principle is that a recognized device name establishes authentication and trust without checking keys.
- For this condition, the applicable principle is that one security mechanism always replaces all other layer-specific access controls.
Explanation
Correct Answer
B:This explains why the most appropriate response is to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests.
Incorrect Answers
A:All traffic within a VLAN is necessarily authorized regardless of identity or policy. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
C:A recognized device name establishes authentication and trust without checking keys. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
D:One security mechanism always replaces all other layer-specific access controls. This is an incorrect generalization for NX-OS local RBAC feature roles. The applicable technical behavior is that rBAC limits administrative actions according to role rules and resource scope. The operator should verify role definitions, assigned users, authorized command tests and accounting logs.
Question 1039
An infrastructure team creates a custom NX-OS role whose rule matches more commands than intended. Assume an engineer instead chooses to rely on switch interface descriptions to enforce management privilege. What is the MOST significant failure introduced by that shortcut?
- The resulting defect is that testing one denied unauthorized connection proves the policy was absent.
- The resulting defect is that a correctly scoped role assignment is the source of the earlier over-privilege.
- The resulting defect is that overbroad permissions undermine separation of duties and permit unauthorized changes.
- The resulting defect is that reviewing an ACI contract causes the pre-existing permit rule to vanish.
Explanation
Correct Answer
C:The proper corrective action is to apply a narrowly scoped NX-OS RBAC role with explicit permitted command sets and verify it through tests. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. In the given case, an infrastructure team creates a custom NX-OS role whose rule matches more commands than intended.
B:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. A correctly scoped role assignment is the source of the earlier over-privilege.
D:This does not explain the actual NX-OS local RBAC feature roles defect after the shortcut. Reviewing an ACI contract causes the pre-existing permit rule to vanish.
Question 1040
An infrastructure team creates a custom NX-OS role whose rule matches more commands than intended. The observed failure is: overbroad permissions undermine separation of duties and permit unauthorized changes. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to disable authorization checks when custom roles require review.
- The controlled remediation is to rely on switch interface descriptions to enforce management privilege.
- The controlled remediation is to use one shared root credential for all users to simplify auditing.
- The controlled remediation is to restrict the role, test permitted and denied commands, and verify session assignments.
Explanation
Correct Answer
D:This addresses the observable fault while preserving a check of the expected result. Validate against role definitions, assigned users, authorized command tests and accounting logs.
Incorrect Answers
A:Disable authorization checks when custom roles require review. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.
B:Rely on switch interface descriptions to enforce management privilege. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.
C:Use one shared root credential for all users to simplify auditing. This would not reliably restore service after the stated fault. Overbroad permissions undermine separation of duties and permit unauthorized changes. The controlled recovery is to restrict the role, test permitted and denied commands, and verify session assignments.