Google Professional Cloud Developer Question 313
Select 3Google Cloud PlatformYou are developing a new feature in a microservices-based application deployed on Google Cloud. To enable safe feature rollouts, you decide to use feature flags. Which of the following practices should you adopt to ensure effective implementation and maintenance of feature flags?
- A
Use descriptive names for feature flags that clearly indicate their purpose.
- B
Remove old feature flags once a feature is fully rolled out and stable.
- C
Hard-code all feature flag logic in the client-side application for better performance.
- D
Implement a centralized configuration management system to manage feature flags.
- E
Use feature flags only for major feature releases and avoid using them for experiments or A/B testing.
Show answer and explanation
Correct answers: A, B, D
Explanation
Feature flags are a powerful tool for managing feature rollouts in dynamic environments like Google Cloud. Best practices include using descriptive names for clarity, removing old flags to avoid technical debt, and leveraging centralized configuration management for scalability. Avoiding client-side hard-coding ensures flexibility, and feature flags can be used for a variety of purposes beyond major releases, such as experimentation and controlled deployment.
- A. Correct.
Using descriptive names helps developers and team members understand the purpose of each feature flag, reducing confusion during implementation and maintenance.
- B. Correct.
Removing old and unused feature flags prevents technical debt and keeps the codebase clean, ensuring long-term maintainability.
- C. Incorrect.
Hard-coding feature flag logic on the client-side is a poor practice as it reduces flexibility and makes it challenging to update flag behavior dynamically without redeploying the application.
- D. Correct.
Centralized configuration management simplifies the handling of feature flags across multiple services and environments, improving consistency and reducing the risk of misconfigurations.
- E. Incorrect.
Feature flags are versatile tools and can be used not only for major feature rollouts but also for experiments, A/B testing, and gradual rollouts. Limiting their use to major releases would reduce their effectiveness.