How does the InnoDB storage engine handle deadlocks when they are detected?

MySQL is installed on a Linux server and has this configuration:
[mysqld]
user=mysql
datadir=/data/mysql/
As the 'root' user, you change the datadir location by executing:
shell> cp -R /var/lib/mysql /data/mysql/
shell> chown -R mysql /data/mysql
What is the purpose of changing ownership of datadir to the 'mysql' user?

A simple master-to-slave replication is currently being used. This information is extracted from the SHOW SLAVE STATUS output:

You execute a 'SHOW CREATE TABLE mytable" on the slave:

The table mytable on the slave contains:

You have issued a STOP SLAVE command. You have determined that it is safe to skip the transaction in this case. One or more statements are required before you can issue a START SLAVE command to resolve the duplicate key error. Which statement should be used?

What is the best method for monitoring Group Replication conflict resolution?

You inherited a busy InnoDB OLTP Instance with 100 schemas and 100 active users per schema.
* Total dataset size is 200G with an average schema size of 2G.
* The data is transient and is not backed up and can be repopulated easily.
* Performance and responsiveness of the DB is paramount.
* The query pattern for the DB instance is split 90/10 read/write.
* DB host is dedicated server with 256G RAM and 64 cores.
One of your colleagues made some recent changes to the system and users are now complaining of performance impacts.
Which four configuration file edits might your colleague have performed to cause the negative DB performance? (Choose four.)