No problem, that’s what the forums are for 
Short answer to this is yes and no, Strapi itself is headless and should remain so when deploying, if you mean to serve the Angular application from the Strapi public folder, the answer to that is, you shouldn’t.
However yes you can deploy both to the same server (I’m not familiar with GCP-AE, if it functions like Heroku then you should have multiple apps, one for each service). What you need is a proxy application such as Nginx, HAProxy, Caddy, Traefik, ect. We have a few guides on our documentation for the usage you are looking for. It’s what we call sub-folder split, for example here is an Nginx Config that achieves what you are looking for: Strapi’s documentation | Strapi Documentation
What this does is:
- Listens on port 80 HTTP, redirects users to port 443 HTTPS (SSL)
- Uses the server_name to direct traffic (thus no issue with ports, as Nginx is what is listening on port 80)
- Accepts traffic for
example.com - Routes all traffic for
example.com/apito the Strapi backend server - Routes traffic for
example.com/dashboardto the Strapi Admin panel - Routes all other traffic to your Angular application being served as a static build (meaning you used
npm run buildand point it at the Angular build folder)
The last point could also be a proxy if your Angular application is server-side rendered, however that goes beyond the scope of the Strapi related documentation hence the warning in the docs about frontend modifications to that config.
Keep in mind, Strapi needs to be aware there is a proxy in front of it, see: Strapi’s documentation | Strapi Documentation
I hope that’s clear, if not please do let me know.