Topic · 10 of 52 questions freeContinuous Integration
Question 1Choose 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.
Choose TWO artifact controls that support traceable releases.
Correct answer:
C. Immutable artifact identifiers
D. Recorded source revision
Answer Option (Which option is correct) C. Immutable artifact identifiers Answer Option (Which option is correct) D. Recorded source revision Explanation:
Option C fixes the artifact identity so a released build cannot silently become different content. Option D records the source revision associated with that build. Together they support tracing a deployment back to both its built bytes and its source inputs.
Why the other options are incorrect:
A. Overwrite released versions silently: Silent overwriting changes content behind an existing release identity. Earlier validation may no longer apply. Immutable identifiers preserve the tested artifact.
B. Deploy whichever latest tag resolves: A mutable latest tag can resolve to different content later. It does not establish which exact build was approved. Traceability needs a fixed content identity.
A registry allows a builder to upload but a deployer only to download. What control is this?
Correct answer:
B. Authorization
Answer Option (Which option is correct) B. Authorization Explanation:
Authorization assigns permitted actions to an authenticated identity. Granting upload to a builder and download to a deployer separates their registry capabilities. The identities can use the same registry while having different rights over its resources.
Why the other options are incorrect:
A. Load testing: Load testing measures workload performance. It does not decide which registry operations an identity may perform. Upload and download rights are permissions.
C. Git merge: Git merge combines source histories. It is not registry access enforcement. Distinct builder and deployer privileges require authorization rules.
D. JSON validation: JSON validation checks document structure and values. It does not grant identity-specific registry rights. Syntax validation cannot substitute for permissions.
A released artifact version must never be overwritten. What registry policy fits?
Correct answer:
C. Immutability
Answer Option (Which option is correct) C. Immutability Explanation:
An immutable release policy rejects attempts to replace an already published version under the same protected identifier. That preserves the relationship between a release identifier and its content. New content should receive a new permitted version or identifier rather than silently changing the existing release.
Why the other options are incorrect:
A. Anonymous write access: Anonymous writing permits unidentified changes to registry content. It does not prevent a release from being replaced. It undermines controlled artifact ownership.
B. Disable checksums: Disabling checksums removes an integrity check. It does not make a release unchangeable. Verification and overwrite prevention should remain enabled where supported.
D. Mutable latest-only tagging: Mutable tagging allows a tag's target to change. That conflicts with the stated no-overwrite requirement. Release identifiers must be protected from reassignment.
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.