Question 450
At Lakeshore Utilities, an infrastructure review by the network resilience team is evaluating field worker private access across a dispersed substation network after a tenant onboarding change (FT-C-15-02). The review finds that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. Any correction must respect this operating requirement: critical substation operations must not use an uninspected fallback. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. Use supported tenant or routing segmentation and restrict access to the correct private prefix as part of Lakeshore Utilities's field worker private access update (FT-C-15-02), while enforcing the constraint that critical substation operations must not use an uninspected fallback. A successful implementation must be checked rather than assumed: In a controlled a dispersed substation network acceptance test, A user belonging to tenant A cannot reach tenant B's overlapping resource; the outcome is recorded under Lakeshore Utilities's rollout (FT-C-15-02). The technical reason is that Private access address overlap must be resolved through explicit routing and identity segmentation.
Incorrect Answers
The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. This option would change the control governed by: Reachable IPsec paths do not grant private application authorization by themselves. That does not resolve the present failure, where private access address overlap must be resolved through explicit routing and identity segmentation. The applicable response is “Use supported tenant or routing segmentation and restrict access to the correct private prefix; validate the decision under controlled load”.
The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. The offered alternative is useful for: Path failover should not silently bypass a mandatory inspection service. In this case the decisive mechanism is: Private access address overlap must be resolved through explicit routing and identity segmentation. The specific action is “Use supported tenant or routing segmentation and restrict access to the correct private prefix; validate the decision under controlled load”.
The source case reports that two private organizations expose the same internal subnet to a shared SASE tenant without isolation. This option would change the control governed by: Edge access models differ by required local platform and management capability. That does not resolve the present failure, where private access address overlap must be resolved through explicit routing and identity segmentation. The applicable response is “Use supported tenant or routing segmentation and restrict access to the correct private prefix; validate the decision under controlled load”.