To trace a real packet is very useful to troubleshoot connectivity issues. It allows you to see all the internal checks that a packet goes through. Add the trace detail keywords and specify the number of packets that you want to be traced. By default, the FTD traces the first 50 ingress packets.
In this case, enable capture with trace detail for the first 100 packets that FTD receives on the INSIDE interface:
> capture CAPI2 interface INSIDE trace detail trace-count 100 match icmp host 192.168.103.1 host 192.168.101.1

Because the report is for non security specialist and will come with recommendations that will help to issues during a period of peaks.
The Firepower System offers two types of reports:
Risk Reports - High-level summaries of risks found on your network.
Standard Reports - Detailed, customizable reports about all aspects of your Firepower System.
Risk Reports
Risk reports are portable, high-level, easy-to-interpret summaries of risks found in your organization. You can use these reports to share information about areas of risk, and recommendations for addressing these risks, with people who do not have access to your system and who may not be network security experts. These reports are intended to facilitate discussion about areas for investment in the security of your network.

To enable Cisco Secure Firewall Malware Defense to detect and block malware, the network administrator must associate a File policy with an access control policy. File policies allow administrators to configure malware detection and file analysis capabilities on the Cisco Secure Firewall Threat Defense appliance.
Steps to configure File policy:
Navigate to Policies > Access Control > File Policies in the FMC. Create a new file policy or edit an existing one to include malware detection and blocking settings. Associate the file policy with the relevant access control policy. Ensure that the access control policy is deployed to the FTD appliance. By associating a file policy, the firewall will inspect files being transmitted through the web server for malware and take appropriate actions (block, allow, or alert) based on the configured rules.

Bobster is referencing local malware analysis requirements, but we have no information that local malware analysis is begin used. By default theat grid is used, and threat grid needs no configuration on the FMC to connect to the cloud. The question states "which configuration tasks"
- we dont need to do anything related to threat grid afaik.