Static moves in linked ELF file, not required entries in .dynsym table

My latest ELF file contains> 500 dynamic moves of type R_ARM_RELATIVE and 5 static moves of type R_ARM_ABS32.
As far as I know, static permutations are only needed for static binding. When loaded, my file will be dynamically linked. I found this information here:
http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf

Static relocations are processed by a static linker; they are normally either
fully resolved or used to produce dynamic relocations for processing by a
post-linking step or a dynamic loader. A well formed image will have no static
relocations after static linking is complete, so a post-linker or dynamic loader
will normally only have to deal with dynamic relocations.

      

        
        
        
      

    

Why does my file contain static permutations while it is fully linked?

My other question is about R_ARM_RELATIVE transitions.
They don't use the .dynsym table for the move process (R_ARM_ABS32 does).
So why is there so many characters (> 70) in the .dynsym table and not 5? Are these symbols used for anything other than the dynamic link navigation process?