Physical SQL AG backup

[Cheapers]

I have read https://www.veeam.com/kb2463, a whitepaper https://www.veeam.com/wp-sql-alwayson-a ... nment.html, the Veeam documentation and several forum threads, but I still have some questions about the backup of a physical SQL AG with the same large database on 1 Primary replica and on 3 Secondary replicas, so 4 copies total (unfortunately, I have no test environment). I am sure everything will work great as always with Veeam, but I like to understand things before implementing.
1) Will the 4 nodes (in the same Protection Group / Backup Job) be backed up 1 by 1 ( 1 after each other)?
2) Will the same database be read 4 times by Veeam on the 4 nodes?
3) If so, how does this fit with SQL AG settings for backups (Prefer Secondary / Secondary only / Primary / Any Replica)?
4) Which Replica will be used for Transaction log backups ( all nodes, 1 node only, or a node as indicated by SQL AG settings (Prefer Secondary / Secondary only / Primary / Any Replica)?
Thanks!

[HannesK]

Hello,
yep, it should "just work"

1) parallel backup will be done as long as there are enough tasks slots free on the repository (probably "it just works")
2) yep
3) for the log backups post192343.html#p192343
4) the preferred one as long as it is available

Best regards,
Hannes