Thank you so much Ashwin, this provides a lot of clarity.

1. Where to deploy Bundles in the workspace

We plan to deploy the bundle using a service principal , so the bundle we plan to deploy under /Workspace/<service_principal>

1. Create notebooks under personal user account
2. Create jobs as .yml files to call these notebooks
3. Push the code to GIT
4. Create bundles
5. Deploy the bundle using azure pipelines using the service principal

This would deploy the bundle under the service_principal account and make it the owner of the jobs as well.
These jobs would be later executed via a seperate secheduling tool called Control-M

2. Source as Azure GIT repo vs Workspace

From your response we understand that the serive principal needs access to GIT if the source type of our jobs is GIT. But if we define jobs with source: WORKSPACE, serive principal
need not have access to GIT.
As these are 2 seperate approaches -> 1. Source type as GIT and 2. Source as Workspace . Is there a benefit of one approach over the other?

3. CI/CD using DAB

We are currently using the python wheel approach , in which we run the pytests as part of the Azure pipeline.
When we are using DAB, whats the best process to run these pytests?
In some places its mentioned that these tests need to be run as a seperate job. I didnt find a place where it defines the best practices for these
pytests when deploying notebooks using DAB

4. Notebooks vs python tasks
If we are deploying purely python script, is there a recommendation of using 1 over the other?
In a python wheel approach, we define an entry point, but dont see an option to do that with notebooks, hence need to call the main function explicity. Is that the correct approach

5. Also, for some reason the links that you provided are not opening correctly, not sure if something got changed while pasting them.

Thank you again for your support, highly appreciate you taking the time to research and respond.

Thanks

Komal