What is Group Policy loopback processing and when would you enable it?

• A. Loopback applies user policies based on the computer's OU, not the user's OU; used for centralized desktop configurations or kiosks
• B. Loopback applies user policies based on the user's OU
• C. Loopback is not supported in modern AD
• D. Loopback duplicates GPOs across domains

Answer: (A)

Loopback processing changes how user policies are determined by tying them to the computer’s location in Active Directory rather than the user’s own organizational unit. This means when someone logs onto a specific computer, the system looks at the computer’s OU to decide which user policies to apply, not just the user's OU. This is exactly what you’d want in environments where you need a consistent desktop experience for everyone who uses that machine, such as centralized desktops, kiosks, labs, or shared terminals.

There are two modes to know about: Merge and Replace. In Merge mode, user policies from both the user’s OU and the computer’s OU are combined, with policies from the computer’s side applying alongside the user’s. In Replace mode, the user policies from the user’s OU are ignored, and only the computer’s OU policies are used. This distinction helps you tailor the behavior to your scenario—Merge for when you want a baseline provided by the computer but still honor the user-specific settings, or Replace when you want a strict, uniform configuration regardless of the user account.

So, enabling loopback processing is appropriate when you need the same desktop configuration for anyone who logs into a particular machine, such as centralized desktops or kiosks. The other statements don’t reflect how loopback processing works or its supported use cases.