Free Oracle 1z0-908 Practice Exam with Questions & Answers

Only internal temporary tables from the optimizer will be created in tmpdir.

Temporary tables will use the InnoDB temporary tablespace located in datadir.

Temporary tables are created in tmpdir only if configured to use MyISAM.

Temporary tables are created in tmpdir only after they reach tmp_tabie_size.

Temporary tables will use the InnoDB temporary tablespace located in /tmp.

The instance deployed on host2 is elected as the new primary instance.

The instance deployed on host3 is expelled from the cluster and must be rejoined using cluster.addInstance ('host3:3377')

The instance deployed on host3 will automatically rejoin the cluster when connectivity is re-established.

Failure of the instance deployed on host1 provokes an outage.

The issuing command cluster.switchToMuitiPrimaryMode() will fail to enable multi-primary mode.

The primary instance can be specified by using the command cluster.setPrimaryInstance(<host>:).

Multiple binary logs can be used to restore data.

Multiple binary logs can be applied in parallel for faster data restoration.

Binary logs are relatively small, and therefore, excellent for long-term storage and disaster recovery.

Binary logs can always be used to unapply unwanted schema changes.

They allow for point-in-time recovery of the data.

ibtmp1

undo_001

ib_buffer_pool

ibdata1

mysql.ibd

ib_logfile0

table data

primary indexes

user privileges

InnoDB Data Dictionary

change buffer

doublewrite buffer

You can provide the root password interactively.

You must manually initialize the data directory.

The MySQL RPM package installation supports deploying multiple MySQL versions on the same host.

MySQL uses the RPM relocatable installation target feature.

The functionality is split among several RPM package files.

You can find the root password in the error log after the first start.

It can be dropped using the DROP ROLE statement.

It is stored in the mysql.role table.

It is created as a locked account.

It can be renamed using the RENAME ROLE statement.

It can be granted to user accounts.

It can be protected with a password.

It executes flush tables with read lock.

It enforces consistent backups for all storage engines.

The backup created is a consistent data dump.

This option uses the READ COMMITTED transaction isolation mode.

It is a cold backup.

Replication will fail because the slave has purged more aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa

transactions than the master.

Replication will fail because the master does not have the required transaction with bbbbbbbb-bbbb- bbbb-bbbb-bbbbbbbbbbbb GTIDs in its binary logs.

Replication will fail because the master has already purged transactions with cccccccc-cccc-cccc- cccc-cccccccccccc GTIDs.

Replication will fail because of inconsistent numbers in cccccccc-cccc-cccc-cccc-cccccccccccc

GTIDs.

Replication will work.

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

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

MySQL Router is restarted.

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