Topic · 10 of 52 questions freeSystem Configuration
Question 21Choose 1
A private host cannot reach a destination because no route exists. What should be inspected?
Correct answer:
D. Route table
Answer Option (Which option is correct) D. Route table Explanation:
A route table determines where packets for a destination are forwarded. Inspect the relevant destination entry, its next-hop target, and its association with the host's network. When the required route is absent, changing application code or credentials does not create the missing network path.
Why the other options are incorrect:
A. YAML comment: A YAML comment is ignored as configuration content. Editing it cannot create a forwarding path. The active routing entries need inspection.
B. SBOM: An SBOM inventories software components. It does not list the network's next-hop decisions. Missing reachability requires route-table analysis.
C. Commit author: The commit author identifies source authorship. It does not determine packet forwarding. The route configuration remains the relevant evidence.
A service address changed but clients still resolve the old address. Which setting affects cache duration?
Correct answer:
D. DNS TTL
Answer Option (Which option is correct) D. DNS TTL Explanation:
A DNS record's TTL specifies how long a cached answer may be retained before refreshing it. Clients or recursive resolvers may continue using the old address while that cached answer remains valid. Review TTL and cache behavior when planning or troubleshooting an address change.
Why the other options are incorrect:
A. HTTP Content-Length: Content-Length describes an HTTP message body size. DNS caching occurs before or independently of that response body. This header cannot expire an old DNS answer.
B. Git major version: The major version communicates software compatibility changes. It is not a DNS cache lifetime. Updating a version number does not refresh cached resolution.
C. File ACL owner: A file ACL owner is a filesystem access attribute. It does not govern resolver caching. DNS records have their own lifetime setting.
A healthy process is removed by the load balancer after a wrong health-check path is configured. What is the fix?
Correct answer:
A. Configure a valid readiness endpoint
Answer Option (Which option is correct) A. Configure a valid readiness endpoint Explanation:
The health check must request a path that reflects the backend's intended readiness and returns an expected response. A wrong path can fail even when the main process is running. Correct the endpoint and verify the resulting health-check status before treating the backend as restored.
Why the other options are incorrect:
B. Increase API token scope: Broader token scope grants additional API permissions. It does not repair the health-check URL. It may add unnecessary privilege.
C. Add more Git branches: More Git branches create additional source histories. They do not change the deployed probe path automatically. Readiness configuration must be fixed.
D. Disable all checks permanently: Disabling all checks removes evidence of backend health. It can send requests to genuinely broken instances. Correct checks are safer than permanently bypassing them.
Topic · 10 of 52 questions freeContinuous Integration
Question 24Choose 1
A pipeline needs database credentials without storing them in Git. Which service fits?
Correct answer:
B. Encrypted secret vault
Answer Option (Which option is correct) B. Encrypted secret vault Explanation:
A secret vault stores sensitive values separately from source code and provides controlled retrieval. The pipeline can obtain the database credential through an authorized identity at runtime. This avoids committing the credential to Git while preserving access control and lifecycle management.
Why the other options are incorrect:
A. Public README: A public README exposes its contents to readers. Database credentials should not be published there. Controlled secret delivery is required.
C. Plaintext artifact: A plaintext artifact retains unprotected secret content. Artifact distribution can spread that exposure. A protected secret store is more appropriate.
D. Docker image label: A Docker image label becomes inspectable image metadata. It is not confidential credential storage. The secret should be supplied through controlled runtime access.
A. True: True conflates two lifecycle actions. Rotation replaces or updates credential material. Revocation invalidates access granted by existing credentials.
A job receives a credential valid for 15 minutes. Which mechanism is involved?
Correct answer:
C. Secret lease expiration
Answer Option (Which option is correct) C. Secret lease expiration Explanation:
A lease associates the issued credential with a defined lifetime. When that lifetime expires, the credential is no longer intended to remain valid under the service's lease policy. The job must plan for the lease duration instead of assuming issued credentials last indefinitely.
Why the other options are incorrect:
A. Git tag deletion: Tag deletion removes a repository reference. It does not expire the issued access credential. Credential validity is governed by its lease.
B. DNS cache expiration only: DNS cache expiration ends use of a cached name answer. It does not invalidate a database password. Secret lifetime is a separate control.
D. Load balancer drain: Load balancer draining stops sending new work to a backend. It does not define a credential's validity period. The described limit belongs to secret leasing.
A 20-minute pipeline uses a credential with a 10-minute lease. Describe a secure way to avoid mid-run authentication failure.
Supplied model answer: Use the approved lease renewal or reauthentication flow before expiry. Keep credentials scoped, avoid logging them, and fail safely if renewed access is refused. Do not extend a static credential indefinitely. Explanation:
Use the approved lease renewal or reauthentication flow before expiry. Keep credentials scoped, avoid logging them, and fail safely if renewed access is refused. Do not extend a static credential indefinitely.
Why the other options are incorrect:
Not applicable: this descriptive response has no option list. The model answer is retained in this explanation; the sample does not establish a compatible free-text answer-field representation.
Verify caller identity Decide permitted actions Invalidate a credential
Supplied source solution: Verify caller identity -> B. Authentication; Decide permitted actions -> A. Authorization; Invalidate a credential -> C. Revocation Explanation:
Verifying who the caller is maps to B, authentication. Deciding what that caller may do maps to A, authorization. Invalidating an issued credential maps to C, revocation. A successful identity check does not itself grant every operation or revoke any prior credential. 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.
Sensitive account values are replaced with surrogate identifiers. What concept fits?
Correct answer:
B. Tokenization
Answer Option (Which option is correct) B. Tokenization Explanation:
Tokenization substitutes a surrogate token for the sensitive account value. Authorized systems may use the token while access to the original value or token mapping remains controlled. This is distinct from merely formatting the original value or storing it unchanged in a different file.
Why the other options are incorrect:
A. Subnetting: Subnetting divides address space into networks. It does not replace sensitive account values with surrogates. The scenario describes data tokenization.
C. Load testing: Load testing measures behavior under demand. It does not transform sensitive values into substitute identifiers. Its purpose is performance validation.
D. Git tagging: Git tagging labels source revisions. Those labels are not surrogates for protected account values. Data substitution is a separate security technique.
A build output should be stored for later controlled deployments. What resource fits?
Correct answer:
A. Artifact registry
Answer Option (Which option is correct) A. Artifact registry Explanation:
An artifact registry stores build outputs so later stages can retrieve the intended version. It can apply access and version controls independently of the source repository. A controlled deployment should select a recorded artifact identity rather than assuming any current output is the validated one.
Why the other options are incorrect:
B. A local temporary log only: A temporary log stores observations and may be discarded. It is not a controlled release-artifact distribution service. Builds need retrievable versioned storage.
C. Interactive shell history: Shell history records entered commands. It does not reliably store the build output for later deployment. Release content belongs in an artifact repository.
D. DNS cache: A DNS cache stores resolution results. It cannot hold and distribute application build packages. Artifact storage serves a different purpose.
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.