<u>Threat </u>is some danger that can exploit a vulnerability.
<h3>What is Threat?</h3>
Threat is seen as Anything that can be able to take advantage of a vulnerability, intentionally as well as accidentally, and take or damage, the asset of a person.
Note that a threat is that which a person or firm is protect against and Vulnerability is seen as Weaknesses.
Therefore, <u>Threat </u>is some danger that can exploit a vulnerability.
Learn more about vulnerability from
brainly.com/question/25633298
#SPJ1
Disk access is way slower than
memory access. Caching is a technique to improve the disk access time. Block cache is a caching technique which
reduces disk accesses time. Here a
portion of disk is bought to cache for reading and a modified blocks are first
changed in cache but reflected in the disk at one go. On the other hand with write through caching
each modified block is written to cache and at the same time it is written to
the disk. Write- through caching
requires more disk I/O so they can have a negative effect on the performance.
Hi, the photo doesn’t show the question on what to answer, all I see are empt boxes, if you message me the question I will answer it for you!
Answer:
The answer is "Referential integrity".
Explanation:
This relates to one aspect of data integrity. Data across multiple tables are linked via relationships. In view of the distinct customer & invoice tables, each invoice table should have the primary key specified throughout the Customer table, for instance. Whenever the invoice table contains a customer ID reference. This ID including its customer will be only a table of the customer.
Answer:
Changing the customer number on a record in the Orders table to a number that does not match a customer number in the customer table would violate referential integrity.
If deletes do not cascade, deleting a customer that has orders would violate referential integrity.
If deletes cascade, customer can be deleted and all orders for that customer will automatically be deleted.
