You would now need to query one of the DAQmx property nodes, likely the Timing property node.
Be careful though -- if you query before the task is started, it might merely give you back your requested rate rather than the nearby actual rate that the hardware supports. That's the behavior I've observed with counter output frequencies. If I request a not-quite-possible frequency and then query before starting the pulse train, DAQmx just dutifully returns my *requested* freq. (Have not re-checked this yet on very recent DAQmx versions).
-Kevin P.
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.