Information on all DML operations (INSERT, UPDATE, DELETE) is captured

By default, information on the audited operations is stored in the tables named AUDIT_LOG_DATA and AUDIT_LOG_TRANSACTIONS which are automatically created in the audited database. Those tables can be moved to a different database on the same SQL Server instance. Learn more on how to do this

Yes. Multiple triggers can exist on the same table

Yes. If a primary key is not found, by default, all fields will be selected as a row key. If the fields contain unique values, the row key can be customized appropriately

The auditing triggers are fired last

Yes

Yes. Windows logins are captured if the change was made by a party authenticating with Windows Authentication

The audit architecture file (.audx) is an XML file that contains all information required to set up database auditing

No. The system tables remain unaffected when auditing is installed

Yes. To do so, execute the stored procedure named dbo.AUDIT_prc_DeleteArchitecture which is automatically created in the audited database

Watches are fields that might not be affected by the data change but are selected to participate in the audit trail. This way, the field is watched when audited fields are changed and its value is added to the auditing report

Yes

Yes

Lookups are watches that pick up their value from a different table. They are used to show a humanly recognizable literal value instead of an ID

Lookup values are derived from a different table. Watches are columns from the same table that aren’t audited but participate in the audit trail

Yes