CompTIA AutoOps + AT0-001 (V1) Exam Practice Test 1

2XX codes indicate success, 3XX codes indicate redirection, 4XX codes indicate a client-side problem, and 5XX codes indicate a server-side problem. Scripts can use these classes to decide whether to continue, follow a redirect, fix the request, or retry later. A 503 is usually worth retrying with backoff, while a 401 needs corrected credentials.

Cloud CLIs load credentials and settings from named profiles, and they fall back to the default profile when none is specified. Passing --profile or setting AWS_PROFILE selects the intended account. Checking the active identity, for example with aws sts get-caller-identity, is a good habit before running commands.

MTBF equals total operating time divided by the number of failures. The service operated for 720 minus 8, or 712 hours, and 712 divided by 4 failures is 178 hours. A higher MTBF means the service fails less often.

An SLO is an internal reliability target for a measured indicator over a period of time. An SLA is a contractual promise to customers with consequences such as service credits. The SLI is the measurement itself, in this case the percentage of successful requests.

Smoke tests are fast, shallow checks that confirm the critical paths of an application work after deployment. A health endpoint check and a basic login flow finish in seconds and quickly reveal a broken release. Load, regression, and penetration testing are valuable, but they are too long and deep to serve as smoke tests.

A canary deployment sends a small percentage of real traffic to the new version and expands exposure as metrics confirm it is healthy. If problems appear, only a small group of users is affected and traffic can be shifted back. Rolling deployments replace instances in batches, but they are not designed around a controlled percentage of users.

Each CI/CD platform reads its own pipeline definition file from the repository. Jenkins uses a Groovy-based Jenkinsfile, GitLab reads .gitlab-ci.yml from the repository root, GitHub Actions reads YAML workflow files under .github/workflows, and Azure DevOps reads azure-pipelines.yml. Keeping pipelines as code allows them to be versioned and reviewed like application code.

A software bill of materials is an inventory of the components, libraries, and versions inside an artifact. Generating one per build and storing it with the matching artifact version lets teams check quickly whether a newly disclosed vulnerability affects a release. An SBOM supports vulnerability management but does not replace scanning or provide encryption.

A webhook sends an HTTP callback from the Git server to the CI system the moment an event such as a push occurs. This removes polling delay and wasted polling requests. A shorter cron interval still polls, and chat or manual triggers rely on a person remembering to act.

Independent jobs can run in parallel, so total time drops from 13 minutes to roughly the longest job, about 6 minutes. The deploy stage still waits for every check to pass, which preserves the quality gate. Running deploy in parallel or first would ship code before it has been validated.

Artifact immutability guarantees that once a version is published, its contents never change. This ensures the artifact that passed QA is exactly what gets deployed. A fix should be published under a new version number rather than overwriting an existing one.

An encrypted key vault keeps secrets out of source control and grants access only to authorized identities. The pipeline fetches the secret at runtime, and the vault can log, rotate, and revoke it centrally. Base64 is only an encoding, not encryption, so anyone with repository access could decode the password.

The YAML specification does not allow tab characters for indentation, so a parser rejects them even when the file looks aligned. Replacing tabs with a consistent number of spaces, typically two per level, fixes the error. Many editors can be set to insert spaces automatically for YAML files.

Bash variables are global by default, so a variable assigned inside a function remains available to the rest of the script after the function runs. Only variables declared with the local keyword are limited to the function. Because ENV_NAME was not declared local, the echo statement prints Deploying to prod.

A messaging queue durably holds messages until a consumer processes and acknowledges them, so work survives consumer downtime. Workers can pull jobs at their own pace, which also smooths out traffic spikes. Synchronous calls fail when the worker is unavailable, and fire-and-forget notifications do not guarantee retention.

SSH is available on virtually every Linux server and allows agentless tools to connect and run commands remotely. Key-based authentication avoids interactive passwords and scales well across many hosts. WinRM is the Windows remoting equivalent, and installing agents adds setup work the scenario does not call for.

Subnet design is the main way to separate internet-facing and internal resources. A public subnet has a route to the internet gateway, while a private subnet does not, so resources inside it cannot be reached directly from the internet. Sharing one subnet or giving databases public IP addresses removes that separation.

Configuration drift happens when a system's actual state diverges from its declared state, often because of manual changes. Configuration management tools detect drift by comparing actual and desired state, then remediate by reapplying the declared configuration. If the manual change was actually needed, it should be added to the code so it is not overwritten again.

A merge conflict means Git found overlapping changes it cannot combine automatically. The developer must open the file, choose or combine the content between the <<<<<<<, =======, and >>>>>>> markers, and remove the markers. Staging the resolved file with git add and committing completes the merge.

An idempotent operation produces the same end state no matter how many times it runs. Blindly appending a line adds another copy on each run, so the result keeps changing. The script should check whether the entry exists, or use a tool module that manages the line's presence, before making a change.

A pre-commit hook that detects secrets stops credentials before they ever enter history. A key that was already committed remains retrievable from earlier commits even after the file is deleted, so it must be revoked and replaced. Indentation linting and squashing later commits do nothing about the exposed credential.

Feature branching isolates each piece of work on its own branch, so it can be reviewed, tested, and merged through a pull request independently. Release branching is aimed at stabilizing and patching a shipped version, not at isolating parallel development. Committing straight to main removes the isolation the lead is asking for.

Docker caches each layer and rebuilds a layer only when its inputs change. Copying requirements.txt and installing dependencies first means that layer stays cached until the dependency list itself changes. Source code copied afterward can change freely without triggering a full reinstall.

jq filters use dot notation to walk JSON objects and square brackets to index arrays. .items selects the array, [0] selects its first element, and .name returns that element's name field. The result is "web01".

The caret (^) anchors a match to the start of a line and the dollar sign ($) anchors it to the end. \d{3} matches exactly three digits, \. matches a literal period, and \s* matches any amount of leading whitespace. Combining anchors, character classes, and quantifiers lets automation extract exactly the lines it needs from logs.