Question 390
At Redfern Aviation, an infrastructure review by the airport infrastructure team is evaluating baggage services reachability across a distributed airport operations network following a complex hub migration (FT-A-16-01). The review finds that a private application SLA probes a public DNS host and reports healthy links while the private service is down. Any correction must respect this operating requirement: airport operations and public guest traffic stay separated. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a private application SLA probes a public DNS host and reports healthy links while the private service is down. Use a probe target and protocol that represent reachability of the private service path as part of Redfern Aviation's baggage services reachability update (FT-A-16-01), while enforcing the constraint that airport operations and public guest traffic stay separated. A successful implementation must be checked rather than assumed: In a controlled a distributed airport operations network acceptance test, The SLA fails when the private-service path is isolated even if general internet access remains healthy; the outcome is recorded under Redfern Aviation's rollout (FT-A-16-01). The technical reason is that Health measurement is useful only when its target reflects the actual application destination.
Incorrect Answers
The source case reports that a private application SLA probes a public DNS host and reports healthy links while the private service is down. This option would change the control governed by: An active physical interface can still be ineligible for an application rule. That does not resolve the present failure, where health measurement is useful only when its target reflects the actual application destination. The applicable response is “Use a probe target and protocol that represent reachability of the private service path; preserve relevant security event evidence”.
The source case reports that a private application SLA probes a public DNS host and reports healthy links while the private service is down. The offered alternative is useful for: Good average latency does not compensate for unacceptable loss for sensitive flows. In this case the decisive mechanism is: Health measurement is useful only when its target reflects the actual application destination. The specific action is “Use a probe target and protocol that represent reachability of the private service path; preserve relevant security event evidence”.
The source case reports that a private application SLA probes a public DNS host and reports healthy links while the private service is down. This option would change the control governed by: Verify participating member state and selection strategy rather than assuming physical link-up means healthy; test both primary and backup paths. That does not resolve the present failure, where health measurement is useful only when its target reflects the actual application destination. The applicable response is “Use a probe target and protocol that represent reachability of the private service path; preserve relevant security event evidence”.