1Y0-370 · Question #2
A school has a pool of mobile devices that students use on premises for coursework. How could a Citrix Engineer configure XenMobile Device Manager to warn the user when the device is taken off campus?
The correct answer is D. Set the Geo-fencing options in a Location Services policy. See the full explanation below for the reasoning.
Question
A school has a pool of mobile devices that students use on premises for coursework. How could a Citrix Engineer configure XenMobile Device Manager to warn the user when the device is taken off campus?
Options
- ADeploy a Roaming Configuration policy.
- BIssue a Locate from the Device Security menu.
- CEnable Tracking from the Device Security menu.
- DSet the Geo-fencing options in a Location Services policy.
How the community answered
(62 responses)- A2% (1)
- B10% (6)
- C6% (4)
- D82% (51)
Community Discussion
9The correct answer is D, setting the Geo-fencing options in a Location Services policy. Geo-fencing lets you draw a virtual perimeter around a physical location like a school campus, and XenMobile will automatically trigger a warning to the user the moment that device crosses outside the boundary, which is exactly what the scenario is asking for. The other options do not accomplish this: Locate and Tracking are reactive or passive tools that help an administrator find a device after the fact, and a Roaming Configuration policy addresses cellular carrier roaming rather than physical location boundaries. When you see a scenario about automated, location-triggered alerts in XenMobile, geo-fencing through the Location Services policy is always going to be your answer.
Geo-fencing in the Location Services policy triggers that alert the moment they leave campus. I almost picked C thinking "Tracking" sounded right, but tracking just logs location, it does not warn anyone.
Geo-fencing is the right call, and it is worth spinning up a quick test in Microsoft Intune or Jamf to see the alert fire in real time, because until you watch that notification pop the moment a device crosses the boundary, the distinction between fencing and tracking stays fuzzy on exam day.
Geo-fencing is the key concept here, where you define a virtual boundary around a location and trigger an alert when a device crosses it, so spinning up a XenMobile lab and configuring a Location Services policy with a geo-fence around your "campus" coordinates is the best way to see this in action. Have you had a chance to look at what other actions you can trigger when a device leaves the defined boundary, like a compliance policy violation or a selective wipe?
The geo-fence lab idea is solid, just keep in mind that XenMobile was rebranded to Citrix Endpoint Management a while back so if you are spinning up a fresh lab you will want to look for CEM in the Citrix docs to avoid chasing outdated screenshots.
Saw this one on my exam and went with A without hesitation. A Roaming Configuration policy is exactly the kind of policy you push out to handle device behavior changes based on network context, and when I was studying the XenMobile policy framework, Roaming Configuration kept coming up in scenarios about alerting users when their device transitions away from a known network environment like a school campus. The geo-fencing option in D sounds tempting but that is more about enforcing boundaries and triggering compliance actions, not specifically warning the user the way the question describes. Roaming Config felt like the cleanest fit for a notify-the-user scenario tied to network presence, and when I walked out of that exam I was confident A was the one.
Toby, your instinct to tie "network transition" to Roaming Configuration makes sense, but that policy is really about managing cellular data roaming behavior, whereas geo-fencing (D) is the feature built specifically to detect when a device crosses a defined location boundary and trigger a user notification in response. The "notify the user" language in the question is the tell, because geo-fencing actions are what fire that kind of alert when a device moves outside a campus perimeter.
Roaming Configuration pushes the off-campus alert automatically, A all day.
Isolde, Roaming Configuration handles user profile roaming, not location-triggered notifications, so it won't fire the alert automatically when a user goes off-campus. D is correct because Location-Based Actions in WEM are what evaluate network context and push the action without any manual trigger.