DTA is a good thing but you should always make the final decision yourself.
You should not blindly believe what DTA or SQL Server Missing indexes suggests you regarding indexes as they do not take into consideration many performance aspects such as update/insert intensity on the the table, they only consider performance enhancement of the certain query/table regardless of the overall workload.
So the answer to your question will be:
This has happened because DTA considers these indexes will improve performance of queries hitting this table.
Over-indexing any table will result in degraded performance on update/insert/delete operations, in more storage used, in longer backup, checkdb, index maintenance operations. It will potentially lead to more intensive use of RAM. As you see - excessive indexes have a lot of drawbacks.
The answer to 3 and 4 - read through the articles recommended below and make sure you understand your workload (read/write activity) and how indexes operate.
It is also a good practice to test such things first and apply in production if necessary.
- SQL101: Indexing Basics by Kimberly Tripp
- Are your indexing strategies working? (aka Indexing DMVs) also by Kimberly Tripp
- SQL Server Index Design Guide in the TechNet Library