Is it worth separating the admin panel from the main site?

Question

CMS

Good day.
Before me there was a task, to write CMS for one site. In the terms of reference, they state that the admin panel should be separate from the outside of the site.
Not even just separately, it must be on a separate subdomain.
Actually the question is, what are the pros and cons of this approach?

Answer 1

The advantages are that scriptkiddies will not break into the admin panel, because they may not even know where exactly to break into.
There are not so many minuses, in fact, the connection should be through the base and a couple of configs that can be duplicated.

Answer 2

In the terms of reference, they state that the admin panel should be separate from the outside of the site.

If this is written word for word, it causes double meanings ... maybe there are more details?
Apart from what - from the frontend, well, that's usually how it is, isn't it? On a domain/subdomain? Another address?

Answer 3

whoever is more comfortable.
if you need it on different domains, it's not difficult in principle. take the engine out of the folders accessible from the web, create two subdomains, in each of them link to the necessary files and that's it. the output will be the admin panel at one address, the site at another, but some data for general use.