A.WHERE user = ‘?’;INSERT INTO members(‘user’,’passwd’) VALUES
(‘[email protected]’,‘secret’);--‘;

B.SELECT id, name FROM user WHERE id=23 OR id=32 AND 1=1;

C.SELECT id, name FROM user WHERE user.id=(SELECT members.id FROM members);

D.SELECT email,passwd FROM members

E.SELECT id, name FROM user WHERE id=23 OR id=32 OR 1=1;

F.WHERE email = ‘INSERT INTO members(‘email’,’passwd’) VALUES
(‘[email protected]’, ‘secret’);--‘;
SELECT user, phone FROM customers WHERE name = ‘\; DROP TABLE users; --‘;

A.MySQL Router is configured based on the information in files in directory_path.

B.MySQL Router configures itself based on the information retrieved from the InnoDB cluster metadata server.

C.MySQL Router is restarted.

D.MySQL Router configures all the cluster nodes based on the information retrieved from the InnoDB cluster metadata server.

A.The frozen file system can be cloned to another virtual machine immediately into active service.

B.Snapshot backups can be used only in virtual machines.

C.There is no need for InnoDB tables to perform its own recovery when restoring from the snapshot backup.

D.Snapshot-based backups greatly reduce time during which the database and applications are unavailable.

E.A separate physical copy must be made before releasing the snapshot backup.

A.Run MySQL Server docker containers.

B.Use systemdwith different settings for each instance.

C.Use system tools to lock each instance to its own CPU.

D.Start mysqldor mysqld_safeusing different option files for each instance.

E.Run mysqldwith --datadirdefined for each instance.

F.Use resource groups to lock different instances on separate CPUs.

A.MySQL writes SDI to the binary log for distributed backups.

B.MySQL Server stores a copy of the serialized data in the InnoDB user tablespace.

C.MySQL keeps InnoDB metadata changes in .sdi files in datadir.

D.The metadata is serialized in JSON format in Serialized Dictionary Information (SDI).

E.MySQL implicitly executes FLUSH TABLES and stores a snapshot backup of the metadata.