See the solution in explanation
Explanation:
FinanceApp software is running as a service named "FinanceApp Service". The service description says "Provides financial data and calculations for the FinanceApp software". The service status is "Stopped", which means that the service is not running and the software is not functional. The service startup type is "Manual", which means that the service needs to be started manually by the user or the administrator. The service log on as is "Local System", which means that the service runs under a predefined local account that has extensive privileges on the local computer.
To fix the issue with the FinanceApp software, you need to do two things:
First, you need to start the service, so that the software can run. To do this, you can right-click on the service name and select "Start" from the menu. Alternatively, you can select the service name and click on the "Start" button on the toolbar. You should see a message saying that the service has started successfully.
Second, you need to change the service startup type, so that the service can start automatically every time the server boots up. This way, you don't have to contact the help desk every time the issue occurs. To do this, you can right-click on the service name and select "Properties" from the menu. Alternatively, you can select the service name and click on the "Properties" button on the toolbar. You should see a window with several tabs and options. On the "General" tab, under "Startup type", you can select "Automatic" from the drop-down list. Then, click on "OK" to save your changes.
By doing these two steps, you should be able to use the FinanceApp software without any problems.
The MarketApp software is running as a service named "MarketApp Service". The service description says "Provides market data and analysis for the MarketApp software". The service status is "Running", which means that the service is running and the software is functional. However, as you reported, the software may crash sometimes, which can cause significant downtime. The service startup type is "Automatic", which means that the service starts automatically every time the server boots up. The service log on as is "TestAccount", which is a test account that was probably used for development or testing purposes.
To fix the issue with the MarketApp software, you need to do one thing:
You need to change the service log on as, so that the service runs under a proper account that has sufficient permissions and security settings for production use. To do this, you can right-click on the service name and select "Properties" from the menu. Alternatively, you can select the service name and click on the "Properties" button on the toolbar. You should see a window with several tabs and options. On the "Log On" tab, under "Log on as", you can select either "Local System account" or "This account". If you choose "Local System account", then the service will run under a predefined local account that has extensive privileges on the local computer. If you choose "This account", then you will need to enter a valid username and password for an account that has appropriate permissions and security settings for running the service. You may need to consult with your IT team or your software vendor to determine which option is best for your situation. Then, click on "OK" to save your changes.

The command that the administrator should issue to configure MySQL successfully is setenforce 0. This command sets the SELinux (Security-Enhanced Linux) mode to permissive, which means that SELinux will not enforce its security policies and will only log any violations. SELinux is a feature that provides mandatory access control (MAC) for Linux systems, which can enhance the security and prevent unauthorized access or modification of files and processes. However, SELinux can also interfere with some applications or services that require specific permissions or ports that are not allowed by SELinux by default. In this case, MySQL may not be able to run properly due to SELinux restrictions. To resolve this issue, the administrator can either disable SELinux temporarily by using setenforce 0, or permanently by editing the /etc/selinux/config file and setting SELINUX=disabled. Alternatively, the administrator can configure SELinux to allow MySQL to run by using commands such as semanage or setsebool.
Reference:
https://blogs.oracle.com/mysql/selinux-and-mysql-v2

The given output in the image indicates that the file is present, but the permissions may not allow it to be read.
The output indicates '-rw-------', which means that the file is set to be readable and writable by the owner only, with no permissions for group or others. To allow the file to be read by users other than the owner, the file's permissions will need to be changed. Thechmod(change mode) command is used to change the file's permissions in Linux. For example,chmod 644 filewould change the permissions of the file to be readable by everyone and writable by the owner, which is typically what's required for a file server. It is always recommended to apply the least permissive settings that still allow the required operation to maintain security.

The subnet mask is most likely containing an error that prevents the application server from communicating with the newly installed database server. The subnet mask is a binary number that defines how many bits of an IP address are used for the network portion and how many bits are used for the host portion. The subnet mask determines which devices belong to the same network or subnet and can communicate directly with each other without routing or switching devices. The subnet mask of the database server is 255.255.O.O, which means that all 32 bits of its IP address are used for the network portion and none for the host portion, which is invalid and makes it unreachable by any other device on any network or subnet. The subnet mask of the application server is 255.O.O.O, which means that only 8 bits of its IP address are used for the network portion and 24 bits are used for the host portion, which is also uncommon and makes it incompatible with most networks or subnets. References: [CompTIA Server+ Certification Exam Objectives], Domain 4.0: Networking, Objective
4.1: Given a scenario, configure network settings for servers.