Either the answer is just plain wrong or the question is sloppily worded.
The appropriate BoL statement is (as quoted in the explanation)
In SQL Server 2005 and later, the SQL Server Profiler graphical user interface displays the Duration column in milliseconds by default, but when a trace is saved to either a file or a database table, the Duration column value is written in microseconds.
So if the trace is viewed in the profiler GUI the duration is shown in milliseconds and the answer given as "correct" is 3 orders of magnitude too small.
On the other hand, maybe the question meant that the trace was setup to write to a table, and the select referred to wasn't what was traced but was a select to read from that table. That's a very different question, and if that had been the question provided then the duration would be in microseconds and the answer provided would have been right.