Answer Option (Which option is correct) A. True

Explanation:

Local scope prevents unintended access through a shared global name.

Why the other options are incorrect:

B. False:

False denies the usual local-scope behavior. Function assignments normally use a local namespace. They do not automatically change global variables.

References:

Python: functions and control flow

Python: built-in types

Answer Option (Which option is correct) A. Convert the value before arithmetic

Answer Option (Which option is correct) D. Validate that the value is numeric

Explanation:

The environment supplies "3" as text, so it must be converted to a numeric type before addition or comparison. Option A makes arithmetic operate on a number. Option D checks that the supplied text represents an acceptable numeric value before conversion and use, so invalid input produces a clear error rather than unintended string processing.

Why the other options are incorrect:

B. Concatenate "1" to increase numerically:

Concatenation joins text rather than adding numbers. Appending a digit produces a different string. Numeric conversion must precede arithmetic.

C. Treat all strings as already numeric:

Strings retain their text type until converted. Their numeric-looking contents do not change that type. Treating them as integers can cause errors or wrong results.

References:

Python: functions and control flow

Python: built-in types

Answer Option (Which option is correct) A. Conditional statement

Explanation:

A conditional statement evaluates whether free space is below the threshold before running cleanup. The action belongs inside the branch whose condition is true. This implements the requirement that cleanup must not run when sufficient space remains.

Why the other options are incorrect:

B. Unconditional loop:

An unconditional loop repeats without requiring low space. It lacks the stated threshold decision. Cleanup could run when it is unnecessary.

C. Git tag:

A Git tag identifies a repository revision. It does not evaluate free disk space. Naming code cannot replace the cleanup condition.

D. Package lock:

A package lock records dependency resolution information. It does not control whether this cleanup executes. The script still needs a threshold check.

References:

Python: functions and control flow

Python: built-in types

Answer Option (Which option is correct) A. Conditional statement

Explanation:

A conditional statement evaluates whether free space is below the threshold before running cleanup. The action belongs inside the branch whose condition is true. This implements the requirement that cleanup must not run when sufficient space remains.

Why the other options are incorrect:

B. Unconditional loop:

An unconditional loop repeats without requiring low space. It lacks the stated threshold decision. Cleanup could run when it is unnecessary.

C. Git tag:

A Git tag identifies a repository revision. It does not evaluate free disk space. Naming code cannot replace the cleanup condition.

D. Package lock:

A package lock records dependency resolution information. It does not control whether this cleanup executes. The script still needs a threshold check.

References:

Python: functions and control flow

Python: built-in types

Answer Option (Which option is correct) B. A destination parameter

Explanation:

A destination parameter lets each caller provide its own backup location while using the same function. The function can validate that input before writing data. Keeping the destination outside the shared implementation avoids a separate hardcoded function for every caller.

Why the other options are incorrect:

A. A commit hash only:

A commit hash identifies a source revision. It does not specify a backup destination by itself. The caller needs an explicit destination input.

C. A syntax error:

A syntax error prevents valid execution. It is not a function input design. Introducing one would break the backup workflow.

D. A hardcoded global destination:

A hardcoded global destination fixes shared configuration outside the call. Different callers cannot supply destinations independently through it. A parameter provides the required flexibility.

References:

Python: functions and control flow

Answer Option (Which option is correct) B. Correlation ID

Answer Option (Which option is correct) C. Timestamp

Explanation:

Option B provides a correlation ID that connects log entries belonging to the same request or automation run. Option C supplies a timestamp that helps reconstruct when those events occurred. Together they support cross-component troubleshooting without disclosing authentication material.

Why the other options are incorrect:

A. Private key:

A private key is secret authentication material. Recording it can enable unauthorized access. Traceability requires nonsecret event metadata instead.

D. Plaintext bearer token:

A bearer token grants access to whoever possesses it. Plaintext logging exposes that capability. Request tracing should preserve context without revealing credentials.

References:

OpenTelemetry: log timestamps and trace correlation

GitHub Actions: secure use