In both cases programs were free to allocate additional memory from DOS, but by default EXE files were loaded in such way that this wasn't necessary and automatically got the largest continuous block of free memory allocated to them (in fact they got the highest addressed block of free memory, but in any sane state of DOS it was also the largest).
IIRC, COM files got all available memory up to the 640K boundary and if you wanted to load additional programs, you had to shrink the preallocated region first.
At the time of DOS, memory access was unrestricted, so, in a basic form, one had direct access to the entire base memory (640k). DOS viruses for example frequently resided just below the top of it, and/or manipulated the interrupt descriptor table (located instead at the very beginning).
https://news.ycombinator.com/item?id=14427269
Remember that they run in an environment with no memory protection.
Of course, you could still access all the memory in the machine by using "far pointers" and far allocators.
http://www.digitalmars.com/download/freecompiler.html
It can be amusing trying to use the C++ standard library given the 64k code size constraint. You can pretty much forget about iostreams...
It's funny how engineers think those times are long gone whereas the demand for very compact systems with low energy footprint is still there. So mastering programming within kilobytes is still a thing, don't disregard it!