100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 650
A transient 503 causes some audit events to disappear because the sender never retries. Independently, reviewers flag this potentially unsafe practice for assessment: 'Publish complete controller secrets in webhook bodies'. Which verification addresses that practice without assuming it caused the incident?
- Inspect signature validation or client identity
- Inspect retry policy and receiver acknowledgments
- Count every retry as a new configuration change
- Inspect payload minimization and transport
Explanation
Correct Answer
D:Sensitive content leaks to downstream storage. The intended behavior is: Audit messages may expose topology and users.
Incorrect Answers
A:This checks authenticate event origin, not the named failure. Receivers must distinguish trusted emitters.
B:This checks retry transient delivery failures, not the named failure. Transient receiver failures should not silently lose events.
C:Duplicate delivery inflates incidents.
Question 651
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. The specific implementation objective is to normalize timeline with offsets. Which configuration best meets the stated requirement?
- Discard healthy comparison devices as irrelevant
- Reboot all switches because one link fault appeared
- Attribute every network fault that day to the new playbook
- Preserve raw timestamps and calculate a documented common time basis
Explanation
Correct Answer
D:Clock skew can invert apparent event order.
Incorrect Answers
A:Missing controls weaken attribution.
B:Broad action can worsen outage.
C:Temporal proximity alone is not causation.
Question 652
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. The specific implementation objective is to join deployment and device events. Which design action is most appropriate for this case?
- Correlate change ID, interface identity and device fault logs
- Sort unrelated device timestamp strings as though clocks match
- Reboot all switches because one link fault appeared
- Discard healthy comparison devices as irrelevant
Explanation
Correct Answer
A:Independent evidence supports causal hypothesis.
Incorrect Answers
B:A false order can misidentify the initiating change.
C:Broad action can worsen outage.
D:Missing controls weaken attribution.
Question 653
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. The specific implementation objective is to preserve negative evidence. What should the engineer implement for this specific objective?
- Check hosts and interfaces that were not changed
- Reboot all switches because one link fault appeared
- Sort unrelated device timestamp strings as though clocks match
- Attribute every network fault that day to the new playbook
Explanation
Correct Answer
A:Control samples narrow the failure scope.
Incorrect Answers
B:Broad action can worsen outage.
C:A false order can misidentify the initiating change.
D:Temporal proximity alone is not causation.
Question 654
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. The specific implementation objective is to identify corrective step. Which adjustment would satisfy this particular constraint?
- Choose rollback or mitigation only after matching the changed state to the fault
- Attribute every network fault that day to the new playbook
- Discard healthy comparison devices as irrelevant
- Sort unrelated device timestamp strings as though clocks match
Explanation
Correct Answer
A:Action should address the supported root cause.
Incorrect Answers
B:Temporal proximity alone is not causation.
C:Missing controls weaken attribution.
D:A false order can misidentify the initiating change.
Question 655
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. The deployment plan must both (1) join deployment and device events and (2) identify corrective step. Which TWO actions together satisfy those requirements? Choose TWO.
- Attribute every network fault that day to the new playbook
- Choose rollback or mitigation only after matching the changed state to the fault
- Correlate change ID, interface identity and device fault logs
- Discard healthy comparison devices as irrelevant
- Sort unrelated device timestamp strings as though clocks match
Explanation
Correct Answers
B:Action should address the supported root cause.
C:Independent evidence supports causal hypothesis.
Incorrect Answers
A:Temporal proximity alone is not causation.
D:Missing controls weaken attribution.
E:A false order can misidentify the initiating change.
Question 656
A nightly Python deployment changes a trunk VLAN and shortly afterward clients lose DHCP service. Three conditions must be met: (1) join deployment and device events; (2) preserve negative evidence; and (3) identify corrective step. Which THREE actions form the narrowest complete plan? Choose THREE.
- Attribute every network fault that day to the new playbook
- Correlate change ID, interface identity and device fault logs
- Check hosts and interfaces that were not changed
- Sort unrelated device timestamp strings as though clocks match
- Choose rollback or mitigation only after matching the changed state to the fault
- Reboot all switches because one link fault appeared
Explanation
Correct Answers
B:Independent evidence supports causal hypothesis.
C:Control samples narrow the failure scope.
E:Action should address the supported root cause.
Incorrect Answers
A:Temporal proximity alone is not causation.
D:A false order can misidentify the initiating change.
F:Broad action can worsen outage.
Question 657
Device logs, pipeline records and syslog timestamps differ by several minutes. Independently, reviewers flag this potentially unsafe practice for assessment: 'Sort unrelated device timestamp strings as though clocks match'. Which inspection most directly evaluates that practice?
- Inspect unaffected-device telemetry
- Reboot all switches because one link fault appeared
- Compare run IDs and affected ports
- Inspect offset and time normalization
Explanation
Correct Answer
D:A false order can misidentify the initiating change. The intended behavior is: Clock skew can invert apparent event order.
Incorrect Answers
A:This checks preserve negative evidence, not the named failure. Control samples narrow the failure scope.
B:Broad action can worsen outage.
C:This checks join deployment and device events, not the named failure. Independent evidence supports causal hypothesis.
Question 658
Device logs, pipeline records and syslog timestamps differ by several minutes. Independently, reviewers flag this potentially unsafe practice for assessment: 'Attribute every network fault that day to the new playbook'. What diagnostic evidence should first be collected to assess that practice?
- Inspect unaffected-device telemetry
- Compare run IDs and affected ports
- Sort unrelated device timestamp strings as though clocks match
- Review causal delta and targeted fix plan
Explanation
Correct Answer
B:Temporal proximity alone is not causation. The intended behavior is: Independent evidence supports causal hypothesis.
Incorrect Answers
A:This checks preserve negative evidence, not the named failure. Control samples narrow the failure scope.
C:A false order can misidentify the initiating change.
D:This checks identify corrective step, not the named failure. Action should address the supported root cause.
Question 659
Device logs, pipeline records and syslog timestamps differ by several minutes. Independently, reviewers flag this potentially unsafe practice for assessment: 'Discard healthy comparison devices as irrelevant'. Which focused check best tests this specific assumption?
- Compare run IDs and affected ports
- Inspect unaffected-device telemetry
- Inspect offset and time normalization
- Reboot all switches because one link fault appeared
Explanation
Correct Answer
B:Missing controls weaken attribution. The intended behavior is: Control samples narrow the failure scope.
Incorrect Answers
A:This checks join deployment and device events, not the named failure. Independent evidence supports causal hypothesis.
C:This checks normalize timeline with offsets, not the named failure. Clock skew can invert apparent event order.
D:Broad action can worsen outage.
Question 660
Device logs, pipeline records and syslog timestamps differ by several minutes. Independently, reviewers flag this potentially unsafe practice for assessment: 'Reboot all switches because one link fault appeared'. Which verification addresses that practice without assuming it caused the incident?
- Compare run IDs and affected ports
- Inspect offset and time normalization
- Discard healthy comparison devices as irrelevant
- Review causal delta and targeted fix plan
Explanation
Correct Answer
D:Broad action can worsen outage. The intended behavior is: Action should address the supported root cause.
Incorrect Answers
A:This checks join deployment and device events, not the named failure. Independent evidence supports causal hypothesis.
B:This checks normalize timeline with offsets, not the named failure. Clock skew can invert apparent event order.
C:Missing controls weaken attribution.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests