Spring Cloud Spring Cloud Configuration Management

Question 1

What is the primary purpose of Spring Cloud Config Server?

Accepted Answer

To provide externalized configuration for distributed systems from a central place

Answer

To manage service-to-service authentication

Answer

To route HTTP requests between microservices

Answer

To aggregate logs from multiple services

Question 2

Which annotation enables a Spring Boot application to function as a Spring Cloud Config Server?

Accepted Answer

@EnableConfigServer

Answer

@EnableConfigClient

Answer

@EnableCloudConfig

Answer

@EnableRemoteConfig

Question 3

By default, where does Spring Cloud Config Server look for configuration files?

Accepted Answer

A Git repository specified by spring.cloud.config.server.git.uri

Answer

A local filesystem directory named /config

Answer

A relational database table named CONFIG

Answer

An environment variable named SPRING_CONFIG_LOCATION

Question 4

What URL pattern does a Spring Cloud Config Server expose to serve configuration for a service named 'payments' in the 'production' profile?

Accepted Answer

/payments/production

Answer

/config/payments-production

Answer

/payments-production.yml

Answer

/api/config?service=payments&profile=production

Question 5

Which Spring Cloud Config feature allows a running service to refresh its configuration without restarting?

Accepted Answer

Spring Cloud Bus with /actuator/refresh or /actuator/bus-refresh

Answer

Hot-swap reloading via JVM agent

Answer

Kubernetes ConfigMap rolling update

Answer

Environment variable substitution at runtime

Question 6

What does the `@RefreshScope` annotation do in a Spring Cloud application?

Accepted Answer

Marks a bean to be re-created when a refresh event is received

Answer

Enables distributed tracing for the annotated component

Answer

Registers the bean with the discovery server on startup

Answer

Creates a new thread pool scoped to each refresh cycle