Question 630
At Evergreen Services, an infrastructure review by the network assurance team is evaluating contractor and staff applications across a regional professional-services firm during a secured remote-work pilot (FT-A-03-02). The review finds that a managed provider plans a common configuration package that mixes two customers' branch address spaces. Any correction must respect this operating requirement: contractors receive only explicitly authorized private resources. Which corrective approach best resolves the observed issue while meeting the operating constraint?
Explanation
Correct Answer
The observed problem is that a managed provider plans a common configuration package that mixes two customers' branch address spaces. Partition tenant-specific templates and administrative scopes while sharing only approved common baselines as part of Evergreen Services's contractor and staff applications update (FT-A-03-02), while enforcing the constraint that contractors receive only explicitly authorized private resources. A successful implementation must be checked rather than assumed: In a controlled a regional professional-services firm acceptance test, A tenant administrator cannot deploy or view another tenant's branch configuration; the outcome is recorded under Evergreen Services's rollout (FT-A-03-02). The technical reason is that Service-provider scale requires isolation of change authority and tenant-specific routing.
Incorrect Answers
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. The offered alternative is useful for: An overlay depends on an underlying reachable transport and does not replace it. In this case the decisive mechanism is: Service-provider scale requires isolation of change authority and tenant-specific routing. The specific action is “Partition tenant-specific templates and administrative scopes while sharing only approved common baselines; test both primary and backup paths”.
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. “Separate routing instances and overlay advertisements with an approved VRF-aware design; limit any exception to authorized flows” addresses the technical dependency: Virtual routing tables can isolate otherwise conflicting IP addressing domains. The reported problem instead follows: Service-provider scale requires isolation of change authority and tenant-specific routing. The more direct correction is “Partition tenant-specific templates and administrative scopes while sharing only approved common baselines; test both primary and backup paths”.
The source case reports that a managed provider plans a common configuration package that mixes two customers' branch address spaces. This option would change the control governed by: Active probes generate measurements while passive monitoring derives evidence from suitable sessions. That does not resolve the present failure, where service-provider scale requires isolation of change authority and tenant-specific routing. The applicable response is “Partition tenant-specific templates and administrative scopes while sharing only approved common baselines; test both primary and backup paths”.