The correct action is Configure table auditing . Copilot summaries and recent-change context for Opportunities, Leads, and Accounts depend on audit history. Microsoft's Dynamics 365 Sales Copilot setup guidance states that when Copilot is enabled, administrators can turn on audit history for the Lead, Opportunity, and Account tables, and Copilot needs audit history to display recent changes for those records.
This issue is not solved by predictive scoring or opportunity pipeline settings. Predictive scoring ranks leads or opportunities based on likelihood, but it does not provide historical summary context. The opportunity pipeline view controls how opportunities are displayed and managed in the pipeline, not what Copilot can summarize. AI insight cards are separate guided insight notifications and are not the underlying data-history source for the missing Copilot summary banner context. Microsoft also documents that Copilot's recent changes list is generated from audit history, and if auditing is turned off, the recent changes configuration is unavailable until auditing is enabled. Therefore, table auditing is the required configuration to make key history available for Copilot-generated summaries and recent-change insights.
References/topics: Copilot in Dynamics 365 Sales; record summaries; recent changes; Dataverse table auditing; Lead, Opportunity, and Account tables.

Explanation:
The correct two UI elements are the Select record type dropdown and one of the Customize field dropdowns on the work item card. In Dynamics 365 Sales, a "company" record is represented by the Account table. The screenshot currently shows the selected record type as Contacts, which would expose contact-related fields such as Full Name, Job Title, and Company Name. That is not the correct entity if the requirement is to display the industry of a company. Therefore, the record type must first be changed to Accounts.
After selecting Accounts, modify the card layout by selecting the Industry field in the Customize section. Microsoft's sales accelerator workspace guidance states that work item appearance can be customized for each record type so sellers see the most relevant information in their work list.
The work item appearance page lets administrators choose the record type and configure the fields displayed on the work item card.
Do not modify Lock customization as the answer target. That controls whether users can personalize the layout; it does not select the account entity or display the Industry field.

Opportunity scoring evaluates multiple relationship signals such as meeting frequency, email engagement, customer responsiveness, and historical behaviors. Increased positive interactions often improve opportunity health and raise the predicted likelihood of successfully closing the deal.

Explanation:
The correct table is Opportunity because the goal measurement is based on deal amounts when opportunities are closed. In Dynamics 365 Sales goal metrics, rollup fields define which table and source attribute are used to calculate actual or in-progress goal values. Microsoft's goal metric documentation gives the direct example of using the Opportunity table with the opportunity actual value/source attribute to track actual money amounts from opportunities closed as Won.
The correct date field is Actual Close Date because the goal period must be determined by when the deal was actually closed, not when the opportunity was created. Microsoft's goal metric configuration guidance states that the Date Field determines the goal period that records roll up into, and gives Actual Close Date as the relevant example.
The correct revenue field is Actual Revenue because the requirement is based on the total deal amount upon closing the opportunity. Budget Amount and Total Amount do not represent the final closed deal value for goal actuals. Goal rollup fields calculate actual performance values for completed measurable results, which fits closed opportunity revenue.