Question-10: Trust in data refers to the conviction that the information maintained by an organisation is accurate and prepared for use. When it comes to making effective use of your data, trust is one of the most important factors to consider. When coupled with culture and agility, it steers a company in the direction of achieving data health. Having complete faith in the information that is kept in your application should be one of your major business goals. First and foremost, you have to have faith that the information you have collected is correct and can serve as a reliable basis for key judgments. In the event that it is not, a single decision made on the basis of erroneous data has the potential to start a snowball effect of further erroneous decisions and actions, severely damaging your organization. You should record any change made to the application's data. In what ways may the validity of your logs be checked by the logging system that you have designed?
A. You should keep a copy of the log both in the cloud and locally at the same time.
B. Make use of a SQL database, and restrict the amount of users who may make changes to the log table.
C. Create a digital signature for each time stamp and log entry, then store the signatures in a secure location.
D. Create a JSON file for each entry in the log, and then save the files to Google Cloud Storage.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 3 Explanation: Option 3: Store a digital signature along with each timestamp and log entry, then digitally sign each timestamp and log item. Answer Options 1, 2, and 4 do not provide any further information that is useful in determining whether or not your logs are real. In addition, Logs may often be exported to cloud storage, BigQuery, and PubSub without too much trouble. Neither exporting to nor storing log data in a SQL database is the most effective method. Simplified Explanation You can use a specific algorithm to generate a digest by hashing each timestamp or log entry, and then digitally sign the digest with a private key to generate a signature in order to verify the authenticity of your logs in the event that they have been altered or forged. This will allow you to determine whether or not the logs have been tampered with. Anyone in possession of your public key has the ability to verify that signature, establishing not only that it was generated with your private key but also determining whether or not the timestamp or log entry was altered. You may keep the log files and the signature files in different folders if you want to do so. Because of this separation, you will have the ability to impose more detailed security standards.