Which statement about the .NET Framework is correct with respect to interoperability and distributed application support?

Introduction / Context:.NET was designed to improve upon legacy COM/DCOM by providing a managed execution environment with modern services. However, it can interoperate with and leverage services from the Windows platform, including COM+ for transactions and distributed components.

Given Data / Assumptions:

• Language interoperability in .NET is achieved by the Common Type System and metadata, not DCOM.
• Transitions between managed and unmanaged code occur via Platform Invocation Services (P/Invoke) and COM interop, not DCOM specifically.
• COM+ services (Enterprise Services) can be used by .NET applications to build distributed, transactional systems.

Concept / Approach:The accurate statement reflects that .NET can consume COM+ (Enterprise Services) for distributed transactions, object pooling, and role-based security. DCOM is not the mechanism for language interoperability or for transitions between managed and unmanaged code in .NET.

Step-by-Step Solution:Eliminate DCOM claims for interoperability and transitions → incorrect for .NET.Confirm COM+ services usage by .NET Enterprise Services → correct.Select the option mentioning COM+ as the valid statement.

Verification / Alternative check:Microsoft documentation describes System.EnterpriseServices and the use of COM+ catalogs/services by managed applications.

Why Other Options Are Wrong:DCOM options misattribute .NET features; .NET uses metadata/IL/CLR, and P/Invoke/COM interop for unmanaged calls.

Common Pitfalls:Conflating COM, DCOM, and COM+; they are related Windows component technologies but distinct from .NET’s managed execution model.

Final Answer:.NET Framework uses COM+ services while creating Distributed Applications.