When executing BloodHound to map Active Directory attack paths, which collector option should be specified via SharpHound to gather computer local admin rights without requiring Domain Admin privileges?
The LocalAdmin collection method queries each computer's local Administrators group via SAM-R, harvesting local admin mappings without needing Domain Admin rights. This directly satisfies the stem's constraint of gathering local admin rights non-privileged, since SAM-R reads rely on standard remote access rather than elevated directory permissions.
Why this answer
SharpHound's LocalAdmin collection method enumerates local administrator rights on computers by querying each machine (via SAM-R, remote registry, or NetSessionEnum depending on privileges) and records which principals have admin access. This data feeds BloodHound's 'AdminTo' edges, which are essential for finding privilege-escalation paths from a low-privileged user to Domain Admin — and it can be collected with only the rights of the invoking user, not Domain Admin.
Exam trap
CPENT often tests whether candidates know the specific SharpHound -CollectionMethod values and what each one gathers — picking a method that sounds related (GPOChanges, TrustList) instead of LocalAdmin is the common error.
How to eliminate wrong answers
Option B (GPOChanges) is wrong because it collects Group Policy object modifications and affected users/computers, not local admin rights. Option C (TrustList) is wrong because it enumerates domain trust relationships, which is unrelated to local admin membership. Option D (DCOptions) is wrong because it collects domain controller configuration and password policy data, not local admin rights on workstations and servers.