A new release should serve 5 percent of users before broader rollout. Which strategy fits?
Correct answer:
D. Canary
Answer Option (Which option is correct) D. Canary Explanation:
A canary release initially exposes the candidate to a small portion of production traffic. Five percent is the limited initial sample specified here. Expansion should depend on the release policy and observed results rather than the initial percentage alone.
Why the other options are incorrect:
A. In-place: In-place updating changes the existing environment. It does not inherently restrict traffic to a small user sample. The percentage-based rollout describes canary exposure.
B. Manual local patching: Manual local patching changes a host directly. It supplies no defined small traffic cohort. A controlled rollout strategy is required.
C. Full immediate replacement: Immediate full replacement exposes the release broadly at once. It removes the intended limited trial. Canary deployment starts with a small group.
Two complete environments allow a fast traffic switch and fallback. Which strategy fits?
Correct answer:
C. Blue-green
Answer Option (Which option is correct) C. Blue-green Explanation:
Blue-green uses two complete environments so traffic can be switched between the active and candidate versions. Retaining the previous environment can make a traffic fallback fast. Shared databases and other mutable dependencies still require a compatible recovery design.
Why the other options are incorrect:
A. Feature branching: Feature branching isolates source changes. It does not create two running environments with traffic switching. Release topology is a different concern.
B. Secret tokenization: Tokenization replaces sensitive values with substitutes. It does not establish active and standby application environments. Blue-green deployment supplies that arrangement.
D. Single-node in-place: Single-node in-place updating modifies the existing host. It lacks the parallel old and new environments described. A traffic switch needs both environments available.
A fleet updates small batches while remaining nodes serve traffic. Which strategy fits?
Correct answer:
C. Rolling
Answer Option (Which option is correct) C. Rolling Explanation:
A rolling deployment updates portions of the fleet while remaining instances continue serving traffic. Old and new versions coexist during the transition. Readiness and compatibility checks matter because requests may reach either version while the update progresses.
Why the other options are incorrect:
A. All-at-once deletion: All-at-once deletion removes serving capacity together. It does not leave unaffected batches available. Rolling updates retain capacity during progression.
B. Git fetch: git fetch downloads repository references. It does not update running fleet instances. Source synchronization is not the deployment strategy.
D. Single-server manual edit: Editing one server manually lacks the defined progressive fleet process. It may create unmanaged differences. The scenario calls for controlled batch updates.
Small initial traffic sample Two complete environments Progressive fleet batches
Supplied source solution: Small initial traffic sample -> B. Canary; Two complete environments -> C. Blue-green; Progressive fleet batches -> A. Rolling Explanation:
A small initial traffic sample maps to B, canary. Two complete environments map to C, blue-green. Progressive fleet batches map to A, rolling. The distinctions concern how traffic or capacity is exposed to the candidate release. Import review: The source solution is preserved above. The sample does not establish the application's ColumnMatch answer representation, so the existing answer-storage fields remain unchanged.
Why the other options are incorrect:
Not applicable: the supplied items are sequence steps or matching choices, rather than incorrect distractors.
The team wants to test expected concurrent user traffic. Which test fits?
Correct answer:
A. Load testing
Answer Option (Which option is correct) A. Load testing Explanation:
Load testing exercises the application under a defined workload, including the expected concurrency. It measures whether response times, errors, and resource behavior meet the intended performance requirements. The workload should represent the relevant user operations rather than only issuing arbitrary traffic.
Why the other options are incorrect:
B. Secret scanning: Secret scanning looks for credential exposure. It does not generate representative concurrent traffic. Workload performance needs a load test.
C. Syntax checking: Syntax checking validates program structure. It does not measure behavior under user demand. Valid parsing is not performance evidence.
D. Git tagging: Git tagging records a source version marker. It does not exercise the service at expected traffic levels. A running workload test is needed.
A bug fix must not break existing functionality. Which test fits?
Correct answer:
B. Regression testing
Answer Option (Which option is correct) B. Regression testing Explanation:
Regression testing checks that a change has not broken behavior that previously worked. The bug fix should be tested together with relevant existing paths and edge cases. This addresses unintended side effects beyond confirming that the single reported bug is fixed.
Why the other options are incorrect:
A. DNS lookup: A DNS lookup tests name resolution. It does not verify all established application behavior. Regression tests cover that behavioral concern.
C. Artifact upload: Artifact upload stores build output. It does not establish that prior features still work. Validation must precede release confidence.
D. Credential issuance: Credential issuance enables access. It is not a test of existing application functionality. Regression checks should exercise the affected behavior.
Answer Option (Which option is correct) A. Defined abort and rollback criteria Answer Option (Which option is correct) C. Representative health metrics Explanation:
Option A defines the conditions for stopping or recovering the canary before rollout begins. Option C supplies representative health measurements for assessing the limited release. Without meaningful observations and a defined response to failures, gradual exposure alone does not provide an effective gate.
Why the other options are incorrect:
B. No observation period: No observation period removes the chance to detect problems in limited traffic. A deployment needs representative health evidence before expansion. Canary risk control depends on that observation.
D. Immediate full traffic on any failure: Full traffic after failure increases exposure to a known unhealthy candidate. It contradicts the purpose of limited rollout. The policy should stop or revert on adverse findings.
Immediately after deployment the team checks login and basic health. Which test fits?
Correct answer:
D. Smoke testing
Answer Option (Which option is correct) D. Smoke testing Explanation:
Smoke testing checks a small set of critical functions immediately after deployment. Login and basic health are examples of those essential checks. A successful smoke test provides an initial signal, but does not replace full regression or performance assessment.
Why the other options are incorrect:
A. Full performance certification: Full performance certification is broader than a quick essential-function check. It can require lengthy workload evaluation. A smoke test is the immediate basic validation described.
B. Git merge resolution: Merge resolution reconciles source conflicts. It does not confirm deployed login and health behavior. Runtime essentials need a post-release check.
C. Static linting only: Static linting examines code without exercising these user flows. It cannot establish that the deployed login works. Basic runtime validation is necessary.
Get exam-ready with a timed AT0 001 CompTIA AutoOps+ V1 mock exam designed to match the official exam's question format, question count, and time limit.