Skip to main content
  1. Public practice questions
  2. AB-650 Practice Exams | Microsoft 365 and AI Services Administrator Associate
  3. AB-650 Practice Exam 1

Question 16 — AB-650 Practice Exam 1

An organization has dozens of branch offices. Windows Location Services is unavailable on client devices, and several branches route through the same public egress addresses. Administrators need Network Connectivity to report each physical office separately and want to define the locations efficiently. Which three actions or configuration principles meet these requirements? (Select three answers)

  1. Use the shared public egress address as the sole identifier for every branch behind that address

  2. Use the Locations tab and import the office definitions by CSV for the portfolio of branches

  3. Assign the LAN subnet range or ranges used by each office

  4. Rely on city-level automatic aggregation to separate branches that share an egress point

  5. Allow the egress IP address to serve as a secondary differentiator after subnet ranges establish which traffic belongs to each office

Correct answers

  1. Use the Locations tab and import the office definitions by CSV for the portfolio of branches

  2. Assign the LAN subnet range or ranges used by each office

  3. Allow the egress IP address to serve as a secondary differentiator after subnet ranges establish which traffic belongs to each office

Explanations

Correct:

Use the Locations tab and import the office definitions by CSV for the portfolio of branches

Office locations can be defined manually through the Locations tab, and CSV import provides a supported way to add a larger portfolio efficiently.

Assign the LAN subnet range or ranges used by each office

LAN subnet ranges identify which internal traffic belongs to each physical location. This enables separate identification even when multiple branches share the same public egress point.

Allow the egress IP address to serve as a secondary differentiator after subnet ranges establish which traffic belongs to each office

After subnet ranges identify the building associated with the traffic, the public egress IP can continue to contribute as a secondary location differentiator.

Wrong:

Use the shared public egress address as the sole identifier for every branch behind that address

An identical public egress address cannot by itself distinguish multiple offices that route through the same external point.

Rely on city-level automatic aggregation to separate branches that share an egress point

Automatic aggregation can combine offices into the same city-level reading and is unreliable for this requirement, particularly when Windows Location Services is unavailable and public egress addresses are shared.