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

RESTful APIs map CRUD operations to HTTP methods. GET reads, POST creates, PUT replaces an entire resource, PATCH applies a partial update, and DELETE removes a resource. Choosing the correct method keeps scripts predictable and aligned with how the API expects to be used.

Machine identities let workloads authenticate as themselves, and federation such as OIDC exchanges a signed job token for temporary cloud credentials. Nothing long-lived is stored, so there is no static key to leak or rotate. Credentials expire shortly after the job ends, which limits the damage if one is exposed.

MTTR is the total repair time divided by the number of incidents. The repair times add up to 200 minutes, and 200 divided by 5 is 40 minutes. Lowering MTTR through better alerting, runbooks, and automated rollback reduces the impact of each failure.

An SLA is an agreement with customers that specifies service levels and remedies when they are missed. Teams usually set internal SLOs tighter than the SLA so they can react before breaching the contract. 99.9% over a month allows only about 43 minutes of downtime, not seven hours.

Regression testing reruns existing tests to confirm that previously working features still behave correctly after a change. It is designed to catch exactly this kind of unintended side effect. Load testing measures performance, and smoke testing is too shallow to verify every payment path.

Blue-green deployment runs two full environments and switches all traffic at once from the old one to the new one. Because the old environment stays intact, rollback is nearly instant. The trade-off is the cost of running duplicate infrastructure during the release.

CI systems expose Git context as variables, such as CI_COMMIT_TAG, CI_COMMIT_BRANCH, and CI_COMMIT_SHA in GitLab. Tags usually mark releases, branches separate environments or workflows, and the commit SHA uniquely identifies the exact code that was built. Pipelines use these values in rules to control which jobs run.

Failure handling should match how critical a step is. Retries absorb transient network errors, and marking a non-critical reporting step as allowed to fail keeps it from blocking a successful release. Rolling back a healthy deployment because of a dashboard error would cause needless disruption.

Scheduled triggers start pipelines at defined times using cron syntax, regardless of code activity. Nightly scans catch newly published vulnerabilities in dependencies that have not changed. Push and pull request triggers only run when someone changes code.

Step dependencies, such as needs in GitLab or depends_on in other tools, tell the orchestrator that one job must finish before another starts. This guarantees the artifact exists before deploy runs. A fixed sleep only hides the race condition and still fails whenever the build takes longer than expected.

Unique, traceable version identifiers let teams deploy or roll back to an exact, known build. A floating tag like latest is overwritten with each publish, so earlier builds cannot be reliably identified. Adding the commit SHA links each artifact directly to its source code.

A leaked credential must be revoked right away, because anyone who copied it can use it until it becomes invalid. Issuing a new token with the smallest required scope limits future impact. Removing the post does not help, since the token may already have been copied.

INI files group key-value pairs under section headers written in square brackets. Without the brackets, the parser treats database as an invalid key line with no value. Correcting it to [database] restores the section so host and port are read correctly.

Assigning to a name inside a Python function creates a new local variable unless the global keyword is used. The function's total exists only while add() runs and does not affect the module-level total. The print statement therefore shows the original value, 10.

FaaS runs short-lived code in response to events and scales automatically with no server management. The provider bills only for execution time, which suits unpredictable, event-driven workloads such as uploads. A polling VM runs and costs money even when there is nothing to process.

Windows Remote Management is the protocol behind PowerShell remoting and lets tools run commands on Windows hosts without an agent. Using the HTTPS listener on port 5986 encrypts the session. RDP is designed for interactive desktop sessions and is not suited to automated command execution.

Health checks let a load balancer send traffic only to instances that respond correctly. A healthy threshold of several consecutive successful checks keeps booting or flapping instances out of rotation until they are ready. Sticky sessions would actually keep users pinned to a bad instance.

IaC tools rely on a state file to map declared resources to real ones. A remote backend gives everyone the same state, and locking ensures only one operation can modify it at a time. Committing state to Git does not prevent concurrent writes and can expose secrets stored in state.

A NameError means the code referenced a name that was never defined in the current scope, often because of a typo or a renamed variable. The script defines retry_count but reads retries. Using a consistent name, or defining the variable before use, resolves the error, and linters can catch these mistakes before runtime.

Release branching keeps a stable branch for each shipped version, so fixes can be applied and released without pulling in new development. The fix is then merged or cherry-picked back into main so it is not lost. Shipping from main would expose customers to unfinished 5.3 features.

git fetch downloads new commits and updates remote-tracking branches such as origin/main, but it does not merge anything into local branches. The developer can inspect the changes, for example with git log main..origin/main, before deciding how to integrate them. git pull would fetch and merge immediately, changing the local branch.

Semantic versioning uses MAJOR.MINOR.PATCH. Backward-compatible fixes increment PATCH, backward-compatible new features increment MINOR and reset PATCH, and breaking changes increment MAJOR and reset the others. Consumers can then judge the risk of an upgrade from the version number alone.

requirements.txt declares a Python project's dependencies, and pinning versions keeps every environment on the same release. The CI job must install from that file before running the script, because a fresh build environment starts without the developer's local packages. Renaming the script to requests.py would actually shadow the real library and cause new errors.

The -i option makes grep's matching case-insensitive, so Timeout and TIMEOUT also match. The -c option prints the number of matching lines instead of the lines themselves. Short options can be combined, so -ic works the same as -i -c.

A for loop iterates over each item in a list and runs the same commands for every element. Adding || exit 1 stops the script as soon as a restart returns a non-zero status. The while true loop never ends, and the case statement only handles one value.