How do you set the build log level to 4 for a BuildConfig named "name" in OpenShift?

How do you set the build log level to 4 for a BuildConfig named "name" in OpenShift?

• A. oc set env bc/name LOGLEVEL="4"
• B. oc set env bc/name BUILD_LOGLEVEL="3"
• C. oc set env bc/name BUILD_LOGLEVEL="4"
• D. oc set env bc/name BUILD_LOGLEVEL=4

Answer: (C)

Setting environment variables on a BuildConfig to influence the build process. Build log verbosity is controlled by the BUILD_LOGLEVEL environment variable. To apply this to a BuildConfig named name, use the oc set env command targeting the BuildConfig and assign BUILD_LOGLEVEL to 4. The correct form is: oc set env bc/name BUILD_LOGLEVEL="4". This updates the BuildConfig so that subsequent builds run with log level 4, giving more detailed output for troubleshooting. Using a different variable name won't affect the build, so LOGLEVEL would be ignored. Providing a different value (like 3) would not meet the requested log level. While omitting quotes often works in the shell, the conventional and explicit form shown uses quotes to denote a string value and matches the exam expectation.

Setting environment variables on a BuildConfig to influence the build process. Build log verbosity is controlled by the BUILD_LOGLEVEL environment variable. To apply this to a BuildConfig named name, use the oc set env command targeting the BuildConfig and assign BUILD_LOGLEVEL to 4. The correct form is: oc set env bc/name BUILD_LOGLEVEL="4". This updates the BuildConfig so that subsequent builds run with log level 4, giving more detailed output for troubleshooting.

Using a different variable name won't affect the build, so LOGLEVEL would be ignored. Providing a different value (like 3) would not meet the requested log level. While omitting quotes often works in the shell, the conventional and explicit form shown uses quotes to denote a string value and matches the exam expectation.