Data Guard :: Archivelogs With FAL Request Created At Different Location?

I tried a Data Guard setup on Oracle Databases (version 10.2.0.4.0, on RHEL)

Primary Database is db5
Standby Database is db6

By the time I created standby database, 3 archivelogs (sequence 11,12,13) were generated on primary which I copied over to standby database server

Now while querying v$archive_gap on the primary database these archivelogs aren't listed
However at the same time querying v$archived_log on either Primary or Standby Database also does not list them

1)
In such case do I need to register these archivelogs on standby database?
Or else do I catalog these archivelogs on standby database?

Also as soon as standby database is started in recovery mode as a part of setup, 1 archivelog (sequence 14) was shown on standby

Now this archivelog has different path than the archivelogs generated later (sequence 15, 16)and v$archived_log shows it is generated as a part of FAL request (FAL=YES)

Question are

1) why it was FALed while redo apply services were active?

2) why this particular archivelog only which is part of FAL request is generated at different location

Does it generate at standby_archive_dest rather than FRA when FAL=YES?

3) why subsequent archivelogs are not part of FAL request or FAL request wasn't needed for subsequent archivelogs?

Primary database init parameters
*.db_name='db5'
*.db_unique_name='db5'

[Code]....