You work as the Microsoft.NET developer at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. All servers in the domain run Windows Server 2003.
The development and deployment of Microsoft.NET Remoting components forms part of your responsibilities at Domain.com. You have just completed developing and deploying a Microsoft.NET Remoting component to a server computer. Microsoft Internet Information Services (IIS) 6.0 is hosting the component. The component runs in an application pool that is configured with the default identity. You received instruction to debug the remote component. You want to do so from your development computer.

What should you do?

A.
Ensure that you have administrative privileges on the server computer.
Then attach the debugger to the generic service host process [scvhost.exe] on the server computer.

B.
Ensure that you have membership of only the Debugger Users group on the server computer.
Then attach the debugger to the ASP.NET Worker Process [w3wp.exe] on the server computer.

C.
Ensure that you have administrative privileges on the server computer.
Then attach the debugger to the ASP.NET Worker Process [w3wp.exe] on the server computer.

D.
Ensure that you have administrative privileges on the server computer.
Then attach the debugger to the COM+ hosting process [dllhost.exe] on the server computer.

Explanation:
You will need administrative privileges on the server computer since only users with administrative privileges can debug remote processes when the process runs under the Network Service account. Since the remote component is hosted by IIS, it means that it is hosted by the w3wp.exe process. And this process runs each application pool under the Network Service Account by default. The w3wp.exe process is the ASP.NET process used to host ASP.NET Web applications, -Web services and .NET Remoting components that are hosted by IIS. Thus the debugger should be attached to the ASP.NET Worker Process [w3wp.exe] on the server computer.
Incorrect answers:
A: The svchost.exe process is used to host Microsoft Windows services that are implemented in DLLs. This should not be attached to the debugger.
B: Members of the debugger Users group on the server computer with non-administrative privileges can debug remote processes only if the processes do not run under the Network Service account. This is not the case in this question.
D: You should not attach the debugger to the dllhost.exe process as this process is used to host COM+ server applications.