Enterprise geodatabase versioned view necessary?

Question

I'm getting some strange behavior when enabling a enterprise geodatabase feature class for versioning to support distributed collaboration.  If I use python and arcpy to enable traditional versioning and global ids

arcpy.management.RegisterAsVersioned(source_table)
arcpy.management.AddGlobalIDs(source_table)

I get an additional table in my enterprise geodatabase - the same name as my source table with _evw appended (mytablename and mytablename_evw for example).

However, if I use ArcGIS Pro catalog pane to do the same thing - register as versioned and add global ids, this evw table is not created.

My question is is this evw table required if all I am using versioning for is to support distributed collaboration with ArcGIS Online.  I'm not even enabling any feature services for editing - just sync

Marcelo Marques · Answer

I suggest going with "Branch Versioning" unless you need some functionality that only "Traditional Versioning" can offer, but "Branch Versioning is the more modern feature.

About your other question.
Truncate Table (Data Management)—ArcGIS Pro | Documentation

* Versioned data is not supported as input. Data must be unregistered as versioned before the tool will run successfully.

These other links might also help.
Configure a map service—ArcGIS Pro | Documentation
Prepare data for use in offline feature services—ArcGIS Pro | Documentation
Enable layers for offline mapping—Portal for ArcGIS | Documentation for ArcGIS Enterprise

Support Services: Feature Service Sync | Esri Training Web Course

Support Services: Perform a Feature Service Sync Manually Via the REST Endpoint | Esri Training Document

Support Services: Deploying and Using ArcGIS Enterprise Services | Esri Training Web Course

DavidSolari · Answer

If all you care about is sync capabilities, enabling Archiving will allow that without having to deal with version management. You can also use Branch Versioning and never create any child versions, this is roughly comparable to classic archiving. In my experience, either do archiving/traditional versioning for every item in your database or use branch versioning for everything, trying to mix the old and new methods leads to compatibility corner cases.

Jay_Gregory · Answer

Thank you @MarceloMarques - I'm curious which versioning I should use in order to _only_ support sync capabilities in my feature services - for distributed collaboration with arcgis online.

https://community.esri.com/t5/arcgis-enterprise-questions/minimum-enterprise-geodatabase-table-config-for/m-p/1307914

Thanks!