UVM scoreboard uses configuration

Should we rely on the configuration such as “test, sequence, agent, env, etc configuration” to check the behavior of DUT in UVM scoreboard?
From my perspective, the scoreboard should not use any configuration of other components (test, sequence, etc) to check. It should monitor the traffic which is in-coming/out-going to/from DUT to analyze and predict the DUT’s behavior only, this way also help to re-use the scoreboard component.

I know, most of people use the configuration in scoreboard to analyze, it help us analyze easily. But it’s not good, am I right?

Thanks.

In reply to chris90:

The scoreboard should monitor the configuration traffic to the DUT to determine how the DUT will behave. It is also common to use the DUT register map to determine DUT behavior. Communication from other components (test, sequence, etc.) is not desired as these components may not exist in every environment.