Which command fetches logs specifically for a BuildConfig, ensuring other log paths are not used?

Which command fetches logs specifically for a BuildConfig, ensuring other log paths are not used?

• A. oc logs buildconfig/<application-name>
• B. oc logs builds/<application-name>
• C. oc logs bcname/<application-name>
• D. oc logs bc/<application-name> --follow

Answer: (D)

Focusing on the BuildConfig resource and streaming its build output is the way to get logs that come specifically from that BuildConfig rather than from other parts of the system. Using the BuildConfig shorthand (bc) targets the BuildConfig itself, and the --follow option streams the log in real time as the build progresses. This combination ensures you’re viewing the logs generated by that BuildConfig’s builds and not logs from unrelated resources like individual builds or application pods. The other options don’t fit because they either reference a different resource type that doesn’t represent a BuildConfig’s logs, point to the Builds resource (which would be logs from Build objects rather than the BuildConfig), or use an invalid resource name.

Focusing on the BuildConfig resource and streaming its build output is the way to get logs that come specifically from that BuildConfig rather than from other parts of the system. Using the BuildConfig shorthand (bc) targets the BuildConfig itself, and the --follow option streams the log in real time as the build progresses. This combination ensures you’re viewing the logs generated by that BuildConfig’s builds and not logs from unrelated resources like individual builds or application pods.

The other options don’t fit because they either reference a different resource type that doesn’t represent a BuildConfig’s logs, point to the Builds resource (which would be logs from Build objects rather than the BuildConfig), or use an invalid resource name.