Skip to content

Commit 70e5ce1

Browse files
Added new questions to IT operations quiz (#7217)
1 parent 0a9bc51 commit 70e5ce1

File tree

1 file changed

+89
-0
lines changed

1 file changed

+89
-0
lines changed

it-operations/it-operations-quiz.md

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -612,3 +612,92 @@ Idea behind the answer: let's go for a quick restart to see whether the problem
612612
- [x] I/O devices
613613
- [ ] memory
614614
- [ ] expansion card
615+
616+
#### Q78. In a hybrid cloud architecture, what is the main challenge of maintaining consistent configuration states across on-premises and cloud environments?
617+
618+
- [ ] Limited network throughput between environments
619+
- [x] Configuration drift due to asynchronous state management and differing IaC tool versions
620+
- [ ] Incompatible authentication mechanisms between providers
621+
- [ ] Lack of hardware abstraction at the virtualization layer
622+
623+
624+
625+
#### Q79. In enterprise IT monitoring, what problem does "cardinality explosion" refer to?
626+
627+
- [x] The exponential growth in metric series when combining multiple label dimensions (e.g., host, service, region)
628+
- [ ] The overuse of alerting thresholds across distributed systems
629+
- [ ] The inability to track metrics due to missing time-series indexes
630+
- [ ] The merging of multiple metric stores into a single pipeline
631+
632+
633+
634+
#### Q80. In a CI/CD pipeline, why is using **immutable infrastructure** considered best practice?
635+
636+
- [ ] It allows manual patching of existing servers to maintain consistency
637+
- [x] It ensures that each deployment creates a new environment instance, preventing configuration drift
638+
- [ ] It eliminates the need for orchestration or automation tools
639+
- [ ] It enables incremental updates instead of full rebuilds
640+
641+
642+
643+
#### Q81. What issue arises when using synchronous microservice calls in a globally distributed production system?
644+
645+
- [ ] Increased CPU utilization in backend servers
646+
- [ ] Reduced need for caching layers
647+
- [ ] Simplified tracing and logging mechanisms
648+
- [x] High inter-service latency and cascading failures under network partitions
649+
650+
651+
652+
#### Q82. In container orchestration systems like Kubernetes, what does the **control plane** primarily manage?
653+
654+
- [x] The desired state of the cluster, ensuring workloads match declared configurations via reconciliation loops
655+
- [ ] The real-time network routing between pods
656+
- [ ] The physical resource allocation at the hardware level
657+
- [ ] The filesystem synchronization across distributed nodes
658+
659+
660+
#### Q83. In distributed systems observability, what is the primary purpose of implementing distributed tracing with context propagation?
661+
662+
- [ ] To record only local system metrics
663+
- [ ] To replicate log data across all services
664+
- [x] To track a single request across multiple services by passing unique identifiers through each span
665+
- [ ] To store trace data directly within the message queue
666+
667+
668+
669+
#### Q84. Why might an SRE team prefer a **Service Level Objective (SLO)** expressed as an error budget over a 100% uptime target?
670+
671+
- [x] Because it balances reliability with development velocity and provides a measurable tolerance for controlled risk
672+
- [ ] Because it enforces stricter deployment rules in CI/CD pipelines
673+
- [ ] Because it automatically configures monitoring alerts based on uptime
674+
- [ ] Because it eliminates the need for any downtime management
675+
676+
677+
678+
#### Q85. What operational issue is most likely if a message broker in an event-driven system begins showing a consistent lag in queue depth?
679+
680+
- [ ] Excessive horizontal scaling of producers
681+
- [x] Consumers are processing messages slower than the production rate, causing backpressure
682+
- [ ] Queue visibility timeout misconfiguration
683+
- [ ] Duplicate message publishing from producers
684+
685+
686+
687+
#### Q86. In large-scale infrastructure management, what’s a key operational advantage of **GitOps** over traditional configuration management approaches?
688+
689+
- [ ] It replaces container orchestration with simple shell automation
690+
- [x] It provides a declarative, version-controlled, and auditable single source of truth for infrastructure state
691+
- [ ] It allows runtime state changes without version tracking
692+
- [ ] It relies solely on imperative deployment scripts
693+
694+
695+
696+
#### Q87. When autoscaling a stateful application, why can horizontal scaling lead to inconsistency issues?
697+
698+
- [x] Because new replicas may lack synchronized persistent state or shared volume access, leading to data divergence
699+
- [ ] Because CPU requests cannot be adjusted dynamically
700+
- [ ] Because vertical scaling is disabled by default
701+
- [ ] Because service discovery protocols fail to register new instances
702+
703+

0 commit comments

Comments
 (0)