Yes, that is also a fine way to solve that problem. Data assets just let you separate those values from the actual blueprint class, which can be useful in some situations.
Data assets can’t be extended with new variables and functions, so if you are going to have a lot of instances of something and you want to guarantee that they are all uniform, data assets are a good use for that.
Data assets also let you more easily SHARE values between blueprint classes, without those blueprints having to share the same parent class.