100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 640
Investigators cannot connect an ACL regression to the job that triggered it because logs omit change IDs. Independently, reviewers flag this potentially unsafe practice for assessment: 'Log raw Authorization headers to debug retries'. Which verification addresses that practice without assuming it caused the incident?
- Emit every informational status as a critical incident
- Inspect redaction and log access policy
- Inspect chronological event records
- Inspect log fields for run and device IDs
Explanation
Correct Answer
B:Credentials may be replayed by log readers. The intended behavior is: Operational observability must not disclose secrets.
Incorrect Answers
A:Noise obscures actual failures.
C:This checks record state transitions, not the named failure. A sequence makes partial failures visible.
D:This checks include stable correlation ID, not the named failure. Cross-system correlation reconstructs cause and effect.
Question 641
A device-change service sends signed callbacks to an internal audit collector. The specific implementation objective is to authenticate event origin. Which configuration best meets the stated requirement?
- Publish complete controller secrets in webhook bodies
- Count every retry as a new configuration change
- Drop every failed webhook after the first send attempt
- Use a documented signature or mutual authentication for webhook delivery
Explanation
Correct Answer
D:Receivers must distinguish trusted emitters.
Incorrect Answers
A:Sensitive content leaks to downstream storage.
B:Duplicate delivery inflates incidents.
C:Short outages cause permanent event gaps.
Question 642
A device-change service sends signed callbacks to an internal audit collector. The specific implementation objective is to retry transient delivery failures. Which design action is most appropriate for this case?
- Use bounded backoff for retryable statuses with unique event IDs
- Publish complete controller secrets in webhook bodies
- Count every retry as a new configuration change
- Accept unsigned arbitrary HTTP posts as device-change evidence
Explanation
Correct Answer
A:Transient receiver failures should not silently lose events.
Incorrect Answers
B:Sensitive content leaks to downstream storage.
C:Duplicate delivery inflates incidents.
D:Anyone could forge audit events.
Question 643
A device-change service sends signed callbacks to an internal audit collector. The specific implementation objective is to make consumer idempotent. What should the engineer implement for this specific objective?
- Drop every failed webhook after the first send attempt
- Accept unsigned arbitrary HTTP posts as device-change evidence
- Deduplicate retried events using stable event identifiers
- Publish complete controller secrets in webhook bodies
Explanation
Correct Answer
C:At-least-once delivery can include duplicates.
Incorrect Answers
A:Short outages cause permanent event gaps.
B:Anyone could forge audit events.
D:Sensitive content leaks to downstream storage.
Question 644
A device-change service sends signed callbacks to an internal audit collector. The specific implementation objective is to protect sensitive payloads. Which adjustment would satisfy this particular constraint?
- Drop every failed webhook after the first send attempt
- Count every retry as a new configuration change
- Send only necessary metadata over TLS to authorized destinations
- Accept unsigned arbitrary HTTP posts as device-change evidence
Explanation
Correct Answer
C:Audit messages may expose topology and users.
Incorrect Answers
A:Short outages cause permanent event gaps.
B:Duplicate delivery inflates incidents.
D:Anyone could forge audit events.
Question 645
A device-change service sends signed callbacks to an internal audit collector. The deployment plan must both (1) authenticate event origin and (2) make consumer idempotent. Which TWO actions together satisfy those requirements? Choose TWO.
- Drop every failed webhook after the first send attempt
- Publish complete controller secrets in webhook bodies
- Use a documented signature or mutual authentication for webhook delivery
- Count every retry as a new configuration change
- Deduplicate retried events using stable event identifiers
Explanation
Correct Answers
C:Receivers must distinguish trusted emitters.
E:At-least-once delivery can include duplicates.
Incorrect Answers
A:Short outages cause permanent event gaps.
B:Sensitive content leaks to downstream storage.
D:Duplicate delivery inflates incidents.
Question 646
A device-change service sends signed callbacks to an internal audit collector. Three conditions must be met: (1) authenticate event origin; (2) make consumer idempotent; and (3) protect sensitive payloads. Which THREE actions form the narrowest complete plan? Choose THREE.
- Drop every failed webhook after the first send attempt
- Use a documented signature or mutual authentication for webhook delivery
- Deduplicate retried events using stable event identifiers
- Publish complete controller secrets in webhook bodies
- Accept unsigned arbitrary HTTP posts as device-change evidence
- Send only necessary metadata over TLS to authorized destinations
Explanation
Correct Answers
B:Receivers must distinguish trusted emitters.
C:At-least-once delivery can include duplicates.
F:Audit messages may expose topology and users.
Incorrect Answers
A:Short outages cause permanent event gaps.
D:Sensitive content leaks to downstream storage.
E:Anyone could forge audit events.
Question 647
A transient 503 causes some audit events to disappear because the sender never retries. Independently, reviewers flag this potentially unsafe practice for assessment: 'Accept unsigned arbitrary HTTP posts as device-change evidence'. Which inspection most directly evaluates that practice?
- Inspect event IDs and de-duplication logic
- Inspect payload minimization and transport
- Inspect signature validation or client identity
- Drop every failed webhook after the first send attempt
Explanation
Correct Answer
C:Anyone could forge audit events. The intended behavior is: Receivers must distinguish trusted emitters.
Incorrect Answers
A:This checks make consumer idempotent, not the named failure. At-least-once delivery can include duplicates.
B:This checks protect sensitive payloads, not the named failure. Audit messages may expose topology and users.
D:Short outages cause permanent event gaps.
Question 648
A transient 503 causes some audit events to disappear because the sender never retries. Independently, reviewers flag this potentially unsafe practice for assessment: 'Drop every failed webhook after the first send attempt'. What diagnostic evidence should first be collected to assess that practice?
- Inspect event IDs and de-duplication logic
- Publish complete controller secrets in webhook bodies
- Inspect signature validation or client identity
- Inspect retry policy and receiver acknowledgments
Explanation
Correct Answer
D:Short outages cause permanent event gaps. The intended behavior is: Transient receiver failures should not silently lose events.
Incorrect Answers
A:This checks make consumer idempotent, not the named failure. At-least-once delivery can include duplicates.
B:Sensitive content leaks to downstream storage.
C:This checks authenticate event origin, not the named failure. Receivers must distinguish trusted emitters.
Question 649
A transient 503 causes some audit events to disappear because the sender never retries. Independently, reviewers flag this potentially unsafe practice for assessment: 'Count every retry as a new configuration change'. Which focused check best tests this specific assumption?
- Publish complete controller secrets in webhook bodies
- Inspect event IDs and de-duplication logic
- Inspect retry policy and receiver acknowledgments
- Inspect signature validation or client identity
Explanation
Correct Answer
B:Duplicate delivery inflates incidents. The intended behavior is: At-least-once delivery can include duplicates.
Incorrect Answers
A:Sensitive content leaks to downstream storage.
C:This checks retry transient delivery failures, not the named failure. Transient receiver failures should not silently lose events.
D:This checks authenticate event origin, not the named failure. Receivers must distinguish trusted emitters.
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.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests