Question 360
For a mobile packet-core transport operator, the change record describes: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. What preventive validation should be standard?
Explanation
Correct Answer
Validate endpoint scheme, port and trust chain before each API integration rollout. This helps prevent recurrence of the issue: An operations client sends an unencrypted HTTP call to a management endpoint that requires TLS and reports a protocol failure as an unreachable routing prefix. Acceptance evidence should be: A controlled request succeeds over authenticated TLS while plaintext attempts are rejected.
Incorrect Answers
Discover supported API transports and model revisions during device enrollment. That is a sensible control for ANOTHER scenario: A provider telemetry collector expects every IOS XR interface state query to use a generic SNMP community string while the device exposes a supported model-driven operational endpoint. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.
Track model-capability inventory and regression-test software upgrades. That is a sensible control for ANOTHER scenario: A controller deploys a single RESTCONF configuration template to devices running different firmware but fails when one model revision lacks the targeted leaf. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.
Require RPC reply and postchange readback checks for configuration jobs. That is a sensible control for ANOTHER scenario: A NETCONF RPC returns an `<rpc-error>` element but a script reports success because the SSH TCP session remained connected. It is less targeted to this issue than: Validate endpoint scheme, port and trust chain before each API integration rollout.