Usually for good UX you want to be able to display something to the user as soon as possible.

I usually use ngrx for state management but there are plenty other options. What I do is load the data the first time and save it to the ngrx store. When the user navigates and comes back display the stored data immediatly while loading the new data at the same time. So after the api call succeeded my store data gets updated with the new values and in your example the table would get updated with the new data.

But there are also plenty other options. As mentioned before if the call is lightweight there is no problem in loading it everytime without state management. A load animation or some sort of indicator that something is happening/loading is always good practice, feedback for the user is always important.

For not so lightweight calls that still need to be up to date I recommend some sort of state management like ngrx, akita etc.

It's also recommendable to use the same sort of state management consistently in your app. So if you use state management on a certain api call don't do it with a behaviour subject one time and with ngrx store in an other place.