An intern is tasked with changing the Anti-Spyware Profile used for security rules defined in...

The Default Prisma Profile referenced in this scenario is one of Palo Alto Networks ' predefined, best-practice profile groups, and predefined profile groups are intentionally locked as read-only in Strata Cloud Manager so that organizations always retain an unmodified, vendor-maintained baseline to fall back on or compare against. This is precisely why the intern sees the fields greyed out regardless of which configuration scope they are working in — it is not a permissions or RBAC limitation, and it is not specific to the GlobalProtect folder, which is why option C is the correct action: the intern must clone or create a new, independently editable Anti-Spyware Profile (and, if the goal is to change what security rules reference, a new profile group as well) rather than attempting to alter the locked default in place. Requesting elevated edit access (option A) will not resolve the issue because the restriction is enforced at the object type level, not the administrator ' s role — even a Superuser cannot directly edit a predefined best-practice profile group ' s membership. Switching to the Prisma Access parent configuration scope (option B) does not unlock a predefined profile either, since the lock follows the object regardless of scope. Option D is a plausible-sounding but incorrect generalization: while it is true best-practice profiles are not intended to be altered, the actionable remedy is to build a new profile, not to attempt further modification of the existing locked one.