Fundraising and Engagement deployment architecture

We have a client who is seeking clarity on the underlying architecture that is created when you deploy the Fundraising and Engagement Azure Services from Solution Center.

Microsoft Cloud Solution Center

Any help with the following client questions would be appreciated.

1. Does the deployment of Fundraising and Engagement Azure Services follow the CAF hub and spoke network model?
2. Can we please see a network architecture drawing for the output of the Fundraising and Engagement Azure Services Deployment (example, hub and spoke with vnets attached, etc)  
3. How many vnets will be deployed in this process?
4. Will any NSG’s be deployed?
5. What Security services will be deployed, i.e. WAF, App gateways, firewalls, etc?
6. What compute services will be deployed, i.e. servers, database servers, bastion, etc.?
7. Can we get a full list of all compute servers/services that will be deployed?
8. Will any load balancers or other network traffic management services get deployed?
9. Can we patch the OS’s of servers with Microsoft monthly security patches?
10. Can we backup the servers using Azure backup?
11. What level of redundancy is used in the Fundraising and Engagement Azure Services deployment, i.e. regions, zones, etc?
12. How do the F&E  Fundraising and Engagement Azure Services and non-compute services get patched or upgraded? Is it redeploying the ARM templates?
13. Is end point protection (i.e. Anti virus) supported on the SQL servers created in the Fundraising and Engagement Azure Services deployment?

We have reviewed all the documentation available on Learn and on Github, and the answers to the above questions are not available. The information on Github is fairly outdated for a release from 2022, while the most current release is from March 2023, and does not offer the type of documentation we are looking for.

Thank you!