What conclusion can you draw?

You work as the Enterprise application 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. Your responsibilities at Domain.com include the support and deployment of applications. There is a Microsoft .NET Remoting component that configured to allow a total of five applications to access data in a C-tree database. All aspects seems to be functional however, you have discovered that whenever it happens that an application accesses data, the other four applications are blocked from accessing the data. To this end you monitor the Contention Rate / Sec performance counter in the .NET CLR LocksAndThreads category and measure it to be 50. You now need to analyze this result.

What conclusion can you draw?

You work as the Enterprise application 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. Your responsibilities at Domain.com include the support and deployment of applications. There is a Microsoft .NET Remoting component that configured to allow a total of five applications to access data in a C-tree database. All aspects seems to be functional however, you have discovered that whenever it happens that an application accesses data, the other four applications are blocked from accessing the data. To this end you monitor the Contention Rate / Sec performance counter in the .NET CLR LocksAndThreads category and measure it to be 50. You now need to analyze this result.

What conclusion can you draw?

A.
Excessive memory is consumed.

B.
Excessive processor time is consumed.

C.
There is a synchronization problem.

D.
There is a platform invocation problem.

Explanation:
It is highly likely that the .NET Remoting component allows only one thread to access the database at a time. The Contention Rate / Sec performance counter measures the rate at which the threads are blocked from acquiring a lock.
Incorrect answers:
A: You cannot use performance counters in the .NET CLR LocksAndThreads category to assume that excessive memory is being consumed.
B: You cannot use performance counters in the .NET CLR LocksAndThreads category to assume that excessive processor time is being consumed.
D: You cannot use performance counters in the .NET CLR LocksAndThreads category to monitor platform invocation issues.



Leave a Reply 0

Your email address will not be published. Required fields are marked *