Q: 9
You discover the ongoing use of the native Dropbox client in your organization. Although Dropbox is
not a corporate-approved application, you do not want to prevent the use of Dropbox. You do,
however, want to ensure visibility into its usage.
Options
Discussion
Option D fits here. With Destination Locations steering exceptions, you can direct Dropbox app traffic to Netskope for inspection, so you get visibility but don't block access. I think A and B would restrict usage, which isn't what they want. Pretty sure D, unless the organization has some unusual routing setup.
Option D
Makes sense to pick D here, since Destination Locations steering exceptions let you monitor Dropbox native client traffic without actually blocking it. That's what the question is after, not restriction. Pretty sure this matches how Netskope expects it set up. Agree?
Yep, it's D.
D tbh. Creating a Destination Locations exception is the right move if you want to see Dropbox app traffic without blocking it.
D imo. If you want visibility into Dropbox native app traffic without blocking, the Destination Locations steering exception is the intended Netskope method. B would just force browser use and isn't what they're after, while A is more SSO-specific and not tied to just Dropbox destinations.
D matches what the question asks for. Not blocking, just need visibility, so Destination Locations makes sense here. Anyone disagree?
D , since you just want to see what users are doing with Dropbox native client, not block it. The Destination Locations exception will steer the traffic so Netskope can monitor it. If blocking was needed B would be more likely, but here D fits better. Pretty sure that's right, but open to other thoughts.
D fits here since the goal is just getting more visibility, not blocking anything. Creating a Destination Locations steering exception lets Netskope monitor native Dropbox client traffic without denying access. Pretty sure that's what they're looking for.
I don't think D is right. I'd actually go with B since blocking the native Dropbox app would force users onto the web version, and then you can monitor their activity there through Netskope. The official guide talks a lot about configuring exceptions for use cases like this, but I'm not 100% sure if this is best for just visibility. Anyone see something different in the practice tests?
Be respectful. No spam.
