Cloud Digital Leader Why cloud technology is transforming business Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Navigate to the Audit Logs page, select the services and log types, save the configuration, then view the logs.

  Why this is correct

  This is the correct order because you first need to access the Audit Logs page to configure settings, then select which services and log types to enable, save the changes to apply them, and finally view the generated logs.

• ✗

  Select the services and log types, navigate to the Audit Logs page, save the configuration, then view the logs.

  Why it's wrong here

  Selecting services and log types before navigating to the Audit Logs page is impossible because the configuration controls for audit log categories (Admin Activity, Data Access, System Event, Policy Denied) are only rendered on that specific page in the Google Cloud console. You cannot pre-select anything from a different screen, and the Cloud Logging API or gcloud commands do not expose a 'pre-navigation' selection state. The correct sequence begins by opening the Audit Logs page, and only then can you toggle the desired services and log types.

• ✗

  Navigate to the Audit Logs page, save the configuration, select the services and log types, then view the logs.

  Why it's wrong here

  Saving the configuration before selecting any services or log types applies the current (default) settings, which does not enable the additional audit log types you intend to turn on. In the Google Cloud console, the Save button persists whatever selections are present at that moment; if you click it prematurely, your subsequent selections remain unsaved and have no effect on the actual logging configuration. This means the saved configuration is incomplete, and the later selections are lost unless you click Save a second time, so the ordering of selecting before saving is mandatory.

• ✗

  Navigate to the Audit Logs page, select the services and log types, view the logs, then save the configuration.

  Why it's wrong here

  Viewing logs before saving the configuration is logically incorrect because audit log entries are generated and written only after the configuration has been applied and persisted to the Cloud Logging system. If you view the Logs Explorer before saving, you will see only pre-existing log entries or none at all for the newly selected services and log types, because the settings have not been activated. The Save operation is the step that finalizes and pushes the configuration to the backend, so it must occur immediately before you attempt to view the resulting audit logs.

Go deeper

Related to this question