Don't be so quick to brand a very-correct answer as "incorrect" merely because you do not yet understand it.
First of all, remember that there are
two kinds of links: "hard" and "soft" (or "symbolic"). The latter is what I was referring to. A "hard" link is an additional reference to the same underlying file-system data structure (the so-called
inode), which will not actually go-away until all of the hard-links are gone. But a "symbolic" link has no skin in the game. If the file(
name) to which it refers is moved or changed in any way, the symbolic link becomes "broken" and can no longer be followed. The symbolic-links are
not tracked and will
not be updated in that case.
"Symbolic links"
are, just as I/we said, "tiny files with file-names in them, flagged to the filesystem as being 'a symbolic link.'" The filesystem will silently follow that chain of filenames ("de-reference" the symbolic link ...) a certain number of times until it either: finds a file, finds a circular reference, or gives up. It will speak to you throughout in terms of the symbolic-link name, not its so-called "target," since the link is what you asked to open and the target is malleable.
You can't "protect" a symlink, and you can't keep the curious from finding out the name of the eventual target. Permissions for "hard" links are, IIRC, actually maintained at the inode level.