Explanation:
Options C, D, and E are incorrect. Legacy logging is deprecated and not recommended for new clusters. Deployments do not guarantee FluentD pods on all nodes, and system & workload logging lacks customization. Options A and B are correct. Disabling logging allows for manual, customized installation, and a Daemonset ensures FluentD pods are deployed on every node for log collection. Reference: https://cloud.google.com/architecture/customizing-stackdriver-logs-fluentd
Ultimate access to all questions.
As a member of a team developing a containerized application for deployment on GKE, you're tasked with ensuring sensitive user data is not logged in Cloud Logging. The application will run on a five-node cluster in a single region. Which two strategies would best meet this requirement?
A
Deploy a custom FluentD daemonset to the cluster that filters out the sensitive information, so it is not logged
B
Enable Cloud Operations in GKE Select System monitoring only (Logging disabled).
C
Enable Cloud Operations in GKE Select Legacy logging and monitoring.
D
Deploy a custom FluentD deployment to the cluster that filters out the sensitive information, so it is not logged
E
Enable Cloud Operations in GKE Select System and workload logging and monitoring
No comments yet.