Answer:
The problems or risk when using a WiFi is that, hackers often have the ability to position themselves between the user and the end point connection. and once these hackers gains access to your information and privacy, u might lose important documents or contents.
It is of utmost importance that when an end user is using a public WiFi as a WAN, he/she must ensure to browse with VPN turned on, and the sharing options turned off.
Explanation:
Solution
One of the biggest risk with public WiFi is the ability or capacity for hackers to position themselves between you (user) and the point of connection. so instead of communicating directly with the hotpot, at several times you end up sending your information to the hacker.
The hacker also have access or privileges to every information you send out such as credit card information, emails and so on. once the hacker gains access to that information, you run into trouble.
As an end user when making use of public WiFi to ensure to browse with VPN (Virtual private Network) on and turned off sharing options
Didn’t you just make a question right now?
Option B
Synchronous replication modes of replication requires a very low latency network connection and ensures data remains in synch with zero data loss in the event of a failure at the source site
<u>Explanation:</u>
Synchronous replication, information is replicated to a subsequent remote place at the identical period as fresh information is implying generated or renewed in the original datacenter. Actually, both master and target roots endure effectively synchronized, which is vital for triumphant crash restoration.
In the circumstances of synchronous replication, this indicates that the write is deemed ended barely when both local and isolated warehouses approve its fulfillment. Therefore, nullity data failure is assured, but the overall execution is regulated down.
Answer:
The answer is reflective DNS attack
Explanation:
Reflective DNS Attack is used in many distributed DDoS attacks to knock down an internet pipe. The attack is divided in two stages: first the attacker sends lots of requests to one or more legitimate DNS servers while using spoofed source IP of the target person, and then, in the second stage, the DNS server receiving the semi-legitimate requests replies to the spoofed IP, thereby unknowingly lauching an attack on the target computer with responses to requests never sent by the victim.