AArch64 systemd service startup and kernel module loading order

Determine whether an AArch64 systemd service unit should declare kernel module dependencies explicitly or rely on implicit module loading before ExecStart. The deployment initializes container networking, making module load failures around service startup a suspected integration boundary.

Kernel module availability varies between AArch64 server boards and Linux distributions. Some AArch64 kernel builds omit optional networking modules by default, and initramfs images can exclude modules needed for network namespace creation. Whether systemd implicitly loads required modules before service startup remains an unresolved integration behavior across distributions.

Should the unit express module dependencies through systemd unit directives, or must the target kernel package guarantee module availability? Does implicit loading behavior differ across AArch64 distributions and board support packages? Which kernel configuration options must be present for the required modules to load reliably?