I remember the sample - so your application has an access token, which is sent in the Authorization header of API calls. This is the token that allows the app to access the Microsoft Graph on the user's behalf. However, this token is short-lived. The token expires an hour after it is issued. This is where the refresh token becomes useful. The OAuth specification introduces a refresh token, which allows the app to request a new access token without requiring the user to sign in again.
Also the above sample app is using the msal-node package - so you do not need to implement any token storage or refresh logic. The app uses the default msal-node in-memory token cache, which is sufficient for the sample application. Production applications should provide their own caching plugin to serialize the token cache in a secure, reliable storage medium.