Translations
Creating a translation clones the source page into a new, publishable draft linked to the original only by matching slug and parent.
A translation isn't a locale-switched view of one page — it's a separate page, with its own id, related to the source only by convention: the same slug and parent, a different locale. Nothing in the database formally links the two rows together.
What "Create translation" does
Creating a translation copies every field from the source, including its full layout, so you start from a complete page rather than a blank one. What it doesn't carry over is identity: the new page always starts life as a draft, no matter what status the source is in, and its id, timestamps, publish date and ownership fields are all its own rather than copies of the source's.
One translation per locale
You can't create a second translation in the same locale for the same source — the server refuses it. A source page and its translations are effectively one variant per slug, parent and locale, so if you need to start a locale over, you edit the translation you already have rather than replacing it with a fresh copy; there's no way to re-clone into an existing locale without deleting that translation first.
What this surface doesn't manage
The set of locales a site supports is configured in code, not here — this surface only shows and manages which pages exist in which locale, not the locales themselves. If a locale you expect to translate into isn't offered when you create a translation, that's a question for whoever maintains the site's configuration, not a setting to look for in this admin.