Question-2: ext4 has a default setting that allows write barriers. Even if the write caches lose power, it makes certain that the metadata for the file system is written to the disc in the proper sequence and in the correct format. There is a penalty to performance as a result of this, particularly for programmes that make heavy use of fsync or that produce and delete a large number of tiny files. On Google Compute Engine, a production database virtual machine will have a persistent disc for data files that is formatted with the ext4 file system. There is very little room left in the database's storage capacity. How can you solve the issue while minimising the length of time the system is offline?
A. Raise the capacity of the persistent drive by making use of the resize2fs command in Linux, which can be found in the Cloud Platform Console.
B. Power down the virtual machine, log into the Cloud Platform Console, and then restart the virtual machine once you have increased the size of the persistent disc.
C. Using the Cloud Platform Console, increase the size of the persistent drive, and then use the fdisk command in Linux to confirm that the additional space is available for usage.
D. Create a new persistent disc that will be associated to the virtual machine, then format and mount it. After that, set the database service to migrate the files to the new disc, and do all of this through the Cloud Platform Console.
E. You may make a snapshot of the persistent disc using the Cloud Platform Console. Restore the snapshot to the new disc, which should be bigger, unmount the previous disc, then mount the new disc, and then restart the database service.

Get All 340 Questions and Answer for Google Professional Cloud Architect