This DOP-C02 practice question tests your understanding of sdlc automation. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
version: 0.2
phases:
install:
runtime-versions:
nodejs: 12
commands:
- npm install
build:
commands:
- npm run build
artifacts:
files:
- '**/*'
discard-paths: yes
Refer to the exhibit. A team uses this buildspec.yml file in AWS CodeBuild. After the build, they expect the artifacts to be placed in a folder structure, but all files are in the root of the output artifact. What is the reason?
Exhibit
Refer to the exhibit.
version: 0.2
phases:
install:
runtime-versions:
nodejs: 12
commands:
- npm install
build:
commands:
- npm run build
artifacts:
files:
- '**/*'
discard-paths: yes
A
The 'files' section only includes '**/*' which does not preserve paths.
Why wrong: The glob '**/*' includes all files but discard-paths causes flattening.
B
The 'discard-paths' option is set to 'yes', which flattens the directory structure.
When discard-paths is yes, all files are placed in the root without preserving paths.
C
The 'base-directory' is not specified, so CodeBuild uses the root of the build output.
Why wrong: Base-directory controls the starting point for artifacts, not path preservation.
D
The 'name' property is missing, causing artifacts to be stored without structure.
Why wrong: The name property sets the artifact name, not the directory structure.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The 'discard-paths' option is set to 'yes', which flattens the directory structure.
Option B is correct because the `discard-paths` option in the `artifacts` section of a buildspec.yml file, when set to `yes`, explicitly flattens the directory structure. This means that even if the `files` glob pattern `**/*` matches files in subdirectories, they are all placed at the root of the output artifact, discarding their original relative paths. Without this setting (or when set to `no`), the directory hierarchy would be preserved.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The 'files' section only includes '**/*' which does not preserve paths.
Why it's wrong here
The glob '**/*' includes all files but discard-paths causes flattening.
✓
The 'discard-paths' option is set to 'yes', which flattens the directory structure.
Why this is correct
When discard-paths is yes, all files are placed in the root without preserving paths.
Related concept
Read the scenario before looking for a memorised answer.
✗
The 'base-directory' is not specified, so CodeBuild uses the root of the build output.
Why it's wrong here
Base-directory controls the starting point for artifacts, not path preservation.
✗
The 'name' property is missing, causing artifacts to be stored without structure.
Why it's wrong here
The name property sets the artifact name, not the directory structure.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the `files` glob pattern `**/*` automatically flattens the structure, but in CodeBuild, path flattening is controlled solely by the `discard-paths` boolean, not by the glob syntax itself.
Detailed technical explanation
How to think about this question
Under the hood, CodeBuild's artifact packaging uses the `discard-paths` flag to control how the `files` glob results are mapped into the output archive. When `discard-paths: yes`, CodeBuild strips all directory components from each matched file path, effectively performing a `basename` operation on every file. This is commonly used when you want to collect all files (e.g., from multiple subdirectories) into a single flat folder for deployment to a simple web server or S3 bucket. In contrast, setting `discard-paths: no` (the default) preserves the full relative path, which is critical for applications that rely on a specific directory hierarchy, such as Lambda functions with nested dependencies.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
SDLC Automation — This question tests SDLC Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The 'discard-paths' option is set to 'yes', which flattens the directory structure. — Option B is correct because the `discard-paths` option in the `artifacts` section of a buildspec.yml file, when set to `yes`, explicitly flattens the directory structure. This means that even if the `files` glob pattern `**/*` matches files in subdirectories, they are all placed at the root of the output artifact, discarding their original relative paths. Without this setting (or when set to `no`), the directory hierarchy would be preserved.
What should I do if I get this DOP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DOP-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.