Best Practice – User Action in an Empty State

Is there an established best practice, backed up by research, that deals with an empty state with multiple CTA for the same action?

For example, this empty state from Dropbox:

There are multiple ways to 'Create a folder'. However, I'm concerned that if a user learns on first usage that the way to create a folder is to click the blue 'Create a Folder' button on the right, will the user not be confused when this button disappears when the empty state is no longer empty?

I am thinking it might be best to show an arrow to a button, 'Click here to create a folder' to teach the user an action that will remain consistent - that button will always be where a user goes to create folders.