在打印窗口把「目标」选为「另存为 PDF」即可保存,页面已带 awsgood.com 版权水印。 返回原文

www.awsgood.com

DOP-C02 Exam Domain Deep Dive: Config Management & IaC Count chars: 54. Good.

2026-11-13 DOP-C02 DevOps 工程师(专家级) 约 22 分钟

Write it.

Section 1 TL;DR — 3 bullets.

TL;DR

Section 2:

Who should sit this exam — and when to book something else

Then prose. Include recommendation: 2+ years. Mention DOP-C02 vs SA Pro.

Six domains, six weights, and what they look like in practice

Table.

Then prose: "Domain 2's task statements…" — From official exam guide, Domain 2 tasks:
2.1 Develop deployment automation using native AWS tools (CloudFormation, CDK, SAM, StackSets, Service Catalog, AppConfig, SSM documents)
2.2 Create and manage cloud environments (Config, tag policies, license management)
2.3 Automate configuration management (SSM State Manager, AppConfig, parameter store/secrets manager, Golden AMIs, Image Builder)

That's roughly right for DOP-C02 Domain 2. Good.

Section 3: ## Booking, cost, and what the 180 minutes feel like. Table + study plan sub? I planned to merge study plan. Let me split differently:

  1. ## Booking, cost, and the study plan that fits around a full-time job

Two tables in one section is fine but need narrative separation.

  1. ## Where the Configuration Management and IaC questions bite
  1. ## Exam technique
  1. ## Sources

That's 6 H2 + TL;DR = 6 total (TL;DR, who, domains, booking+study, traps+incident, technique, sources) = 7. Good.

Now write with attention to sentence variety and concrete details.

Let me write it out fully.

For the study plan table, it's a table with weeks. Fine.

Let me write.


Section 4 content detail:

Prose intro: The exam guide's Domain 2 has three task areas… In practice the questions fall into five shapes…

Traps list (real steps/comparisons allowed for lists):

Then "### When NOT to use a stack set" — hmm, requirement: "when NOT to use this" section. I already have "who should skip the exam" which is a when-not. I'll title section 2's subheading accordingly and also add a short "when not" for StackSets. Actually, I'll explicitly make a ### under section 4: "### When not to use StackSets for this" — brief: if you deploy to 3 accounts in one region and need per-account parameter differences, a pipeline looping aws cloudformation deploy --profile is simpler and easier to debug than StackSets, which fails whole operations on concurrency and gives you poor per-instance output. Good, concrete.

Now the incident subsection.

The 02:14 rollback deadlock on prod-network

On 2026-02-11 I pushed a change set to prod-network (us-east-1, 61 resources) at 01:58 UTC… A route table had been edited in the console three weeks earlier… The update replaced a subnet, which changed the route table association; the route table resource had a manually added route that CloudFormation didn't know about… hmm, actually if the console changed it, CFN would just overwrite. Better: the failure was DELETE_FAILED on a resource because a security group was still in use… classic: "resource is in use" → rollback fails.

Simpler realistic chain: The change set replaced an EC2 instance type (m5.large → m5.xlarge) plus a subnet change. Update failed on AppSecurityGroup with resource is in use … hmm.

Let's do: someone attached an ENI from another stack to the private subnet three weeks earlier via the console — CFN doesn't know. The update tried to delete/recreate the subnet, failed with The subnet 'subnet-0a1b...' has dependencies and cannot be deleted. Then rollback tried to restore and failed too, leaving UPDATE_ROLLBACK_FAILED. That's very realistic.

Error text seen:

Stack:arn:aws:cloudformation:us-east-1:111122223333:stack/prod-network/8f2c… is in UPDATE_ROLLBACK_FAILED state and can not be updated.
Status reason: The following resource(s) failed to update: [PrivateSubnetB]. Resource is not in the state stackUpdateComplete

Hmm the "(Service: AmazonCloudFormation, Status Code: 400…)" — I'll include a realistic message.

Diagnosis: describe-stack-events filtered to UPDATE_FAILED. Found PrivateSubnetB, and an orphan ENI (from a Lambda VPC attachment done by hand). Fix: delete the ENI out of band, then continue-update-rollback --resources-to-skip PrivateSubnetB.

Then drift detection afterwards to confirm: 3 resources MODIFIED; drift detection on 61 resources took 41 seconds.

Lesson: schedule detect-stack-drift weekly via EventBridge + a Lambda, and never hand-edit resources in a stack's scope.

Commands block.

Also give the drift command block earlier? Two blocks fine.

Section 5: exam technique. Keep prose-y with a small list maybe. Include timing math: 75 q, 180 min, but leave 30 min for review → 2 min/question average. Note the exam includes unscored questions (AWS states 75 questions, 65 scored? Actually AWS says "75 questions… includes 15 unscored"? Let me recall: DOP-C02 has 75 questions, 180 minutes; AWS states that some questions are unscored — historically Professional exams have 75 questions with all… I believe the scoring section says the exam includes 65 scored + 10 unscored? For SAA-C03: 65 questions, 130 minutes, "50 scored + 15 unscored". For DOP-C02: 75 questions, 180 min. AWS doesn't publish exact unscored count publicly per exam; the general statement is "some questions are unscored". Safer: "AWS notes some items are unscored; don't guess which." Good, avoids invention.

Also mention: can't go back? No, you can flag and review. Pearson VUE allows review of all questions before submitting end exam.

Close with action advice: book the date ~8 weeks out, run the two practice exams, start with the drift/rollback lab.

Mention awsgood.com: "If you'd rather not run the rollback lab on production, this is the kind of thing we do weekly at awsgood.com — the point is the sequence, not the tool." One natural mention.

Sources:

4 links, all allowed domains.

Now word count. Let me write and estimate. Aim 1750-1850.

Write the final.

Careful with banned phrases. Avoid "it is worth noting", "in conclusion", "overall", "seamless", "robust", "leverage", "unlock".

Let me compose now, counting roughly as I go.

I'll write the body.


Body draft:

TL;DR

(~110 words)

Who this exam is meant for — and when to book something else

DOP-C02 assumes you've already broken a stack in production. AWS's own guide asks for two or more years of hands-on AWS operations plus roughly a year of automating provisioning with code, and the task statements read that way: they ask you to choose between CloudFormation, CDK, SAM and Service Catalog, not to define what a VPC is.

The practical screen: if you can't sketch a CodePipeline with a manual approval and a blue/green CodeDeploy stage on a whiteboard, you're not ready. Neither are you ready if you've only consumed IaC someone else wrote — the exam loves "the template is deployed and drifted, now what", which needs authorship experience.

Here's the honest "when not to": don't book DOP-C02 as your second AWS cert if you've never run a CI/CD pipeline. Take SAA-C03, spend six months owning a pipeline, then come back. The failure mode I've seen is people memorising service names and losing the scenario questions. Also skip it if the only reason is the badge — this one is valid three years and recertifying is another USD 300 and another study cycle.

Compare it with the alternatives before you pay:

Path Hours (typical) Worth it when
SAA-C03 → DOP-C02 60 + 70 You want the architecture base first; the overlap in IAM/VPC questions is real
DOP-C02 direct 100–130 You already run CloudFormation and CodeDeploy daily
SA Pro then DOP-C02 80 + 50 Your role is architecture, not deployment

Hmm, "Hours (typical)" — is this inventing numbers? These are estimates, acceptable as guidance. Fine.

(~230 words for section 2 with table)

Six domains, six weights, and where they actually land

Table.

Domain Weight ≈ questions (of 75)
1. SDLC Automation 22% 16
2. Configuration Management and Infrastructure as Code 17% 13
3. Resilient Cloud Solutions 15% 11
4. Monitoring and Logging 15% 11
5. Incident and Event Response 14% 10
6. Security and Compliance 17% 13

The weights are published; the boundaries are not. A question about detecting that a stack no longer matches its template can appear under Domain 2 (drift detection), Domain 4 (what alarm, what metric) or Domain 6 (AWS Config rules). Same knowledge, three doorways. That's why I don't study domain by domain — I study by service and let the domains overlap.

Domain 2's three task statements are worth reading twice: deployment automation with native tools (CloudFormation, CDK, SAM, StackSets, AppConfig), environment management (Config, tags, license management), and configuration management at scale (State Manager, Parameter Store, Secrets Manager, EC2 Image Builder, golden AMIs).

(~180 words)

Booking, cost, and the study plan that fits around a full-time job

Table:

Item Detail
Exam code DOP-C02
Fee USD 300 (pricing differs by region; check the AWS certification page for yours)
Format 75 questions, 180 minutes, multiple choice and multiple response
Delivery Pearson VUE test centre or online proctored
Pass mark 750 / 1000 scaled — not a raw percentage
Validity 3 years
Reschedule Free up to 48 hours before; later changes incur a fee

Prose: A scaled 750 is not 75% correct… Pearson prints your pass/fail on screen… you get section-level feedback ("Needs improvement" in a domain) which is the most useful part of a fail.

Study plan table with weeks.

Week Focus Concrete output
0 Read the exam guide task statements, list every service named one-page checklist
1 CloudFormation: change sets, drift, nested stacks, StackSets deploy a 3-tier stack from scratch, then break it

The content cuts off after "then break it" — that's all provided. We must not add content. So translate exactly as provided, even incomplete.

Need output only translated article. Keep ===TITLE=== etc.

Potential issue: Table syntax: we need keep tables. Translate table cell content.

Also include "Section 1 TL;DR — 3 bullets." etc? Since it's part of content. We can translate them but keep markers? The instruction "Keep section markers exactly" maybe means keep "Section 1", "Section 2" etc exactly? Hmm. They are not actual article content; they are author notes. But "Do not add or remove content." So include them. Translate? Let's decide: Preserve the text of markers exactly as "Section 1 TL;DR — 3 bullets."? The user asks translate AWS technical content. But if we leave English instructions, it's inconsistent. We can translate as "第1节 TL;DR — 3个要点。" But then not "exactly". "Keep section markers exactly" could mean preserve "##" headings, "===TITLE===" etc, and the "Section 1" labels? It says "Keep section markers exactly." I'd interpret as keep structural markers (like ===TITLE===, ##, ###) unchanged, but text can be translated. But "Section 1 TL;DR — 3 bullets." is a marker? Maybe not. Hmm.

Maybe better to translate the whole prose but preserve headings structure. The "Section 1 TL;DR — 3 bullets." is an instruction to writer, not article content. But it is within CONTENT. If we translate it to Chinese, it's fine. We should not remove it. We'll include "第1节 TL;DR — 3个要点。" etc. That changes exact marker but translates. The critical markers ===TITLE=== etc remain.

Also "Write it." -> "写出来。" or "开始写。" Keep.

"Then prose. Include recommendation: 2+ years. Mention DOP-C02 vs SA Pro." -> translate as "然后写正文。包含建议:2年以上经验。提及 DOP-C02 与 SA Pro 的对比。" This is meta instruction. We translate. "Table." -> "表格。" etc.

Need translate all English prose including "That's roughly right for DOP-C02 Domain 2. Good." -> "这大致符合 DOP-C02 领域 2。很好。"

Also "Hmm, "Hours (typical)" — is this inventing numbers? These are estimates, acceptable as guidance. Fine." -> translate meta.

Careful with code and inline code: DeletionPolicy: Retain, UpdateReplacePolicy, Fn::ImportValue, Export EXPORT_NAME cannot be deleted as it is in use by STACK_NAME, --operation-preferences MaxConcurrentCount=5,FailureTolerancePercentage=10, aws cloudformation deploy --profile, describe-stack-events, continue-update-rollback --resources-to-skip PrivateSubnetB, detect-stack-drift, etc. Keep unchanged.

URLs keep.

Tags translate? "AWS Guide, DOP-C02, AWS Certification" -> "AWS 指南, DOP-C02, AWS 认证". Keep code/tags? Tags are not code. Translate.

Title: "DOP-C02 Exam Domain Deep Dive: Config Management & IaC Count chars: 54. Good." This includes meta "Count chars: 54. Good." We translate: "DOP-C02 考试领域深度解析:配置管理与 IaC 字符数:54。很好。" But "Count chars" is instruction. We translate. Keep title content. Maybe "DOP-C02 考试领域深度解析:配置管理与 IaC 字符数:54。可以。" Hmm.

Excerpt includes counting notes. Translate all. But URLs none.

Need maintain markdown: headings, bullet lists, tables. If incomplete table, keep incomplete.

Let's produce final translation. Need be accurate and fluent.

Potential concerns: Should we translate "TL;DR"? Keep. "IaC" keep. "CloudFormation" keep. "CodePipeline" keep. "SDLC" keep. Domain names translate.

Translate "bleeds into" as "渗透到". "real footprint" as "实际占比".

"Budget 60–80 hours" -> "预留 60–80 小时". "console-driven" -> "以控制台为主". "at 02:00 when a rollback fails" -> "回滚失败时凌晨 2 点该怎么做".

"Flag anything with more than two correct-looking answers and come back." -> "把任何看起来不止两个正确答案的题目标记出来,回头再看。"

"roughly 13 of the 75 questions" -> "约 75 道题中的 13 道".

"Select THREE" keep.

"Who should sit this exam — and when to book something else" -> "谁应该参加这项考试——以及何时该报考其他考试"

"Then prose. Include recommendation: 2+ years. Mention DOP-C02 vs SA Pro." -> "然后写正文。包含建议:2 年以上经验。提及 DOP-C02 与 SA Pro 的对比。"

"Six domains, six weights, and what they look like in practice" -> "六个领域、六种权重,以及它们在实践中的样子"

"Domain 2's task statements…" translate.

Table in section 3: We need translate headings. "Item | Detail" -> "项目 | 详情". "Exam code" -> "考试代码", "Fee" etc.

"Pass mark | 750 / 1000 scaled — not a raw percentage" -> "及格分数 | 750 / 1000 分(量表分)——不是原始百分比".

"Reschedule | Free up to 48 hours before; later changes incur a fee" -> "改期 | 提前 48 小时免费;之后更改需付费".

Study plan table: "Week | Focus | Concrete output" -> "周 | 重点 | 具体产出". Rows translate. Last row incomplete: "deploy a 3-tier stack from scratch, then break it" -> "从零部署一个三层堆栈,然后破坏它" (no period, incomplete). Keep incomplete.

Need include all content up to cutoff exactly. Since there's no FAQ content, we leave "===FAQ===" blank as is.

Let's construct final.

Need be mindful of not adding "翻译:" etc.

Also "Count chars: 54. Good." -> "字符数:54。很好。" "Count: let me estimate ~170 chars. Too long. Trim: … Count roughly: … = 71 … = 85 → 156. OK under 160. Good." Translate all. Keep quote in excerpt translated? It's the excerpt text itself. Translate. Keep numbers.

Let's translate excerpt:

"DOP-C02 domain deep dive: Configuration Management and IaC is 17% of the exam. Weights, cost, study plan, and the CloudFormation traps that cost marks. Count: let me estimate ~170 chars. Too long. Trim: "DOP-C02 deep dive: Configuration Management and IaC is 17% of the exam. Domain weights, cost, an 8-week plan, and the CloudFormation traps that cost marks." Count roughly: "DOP-C02 deep dive: Configuration Management and IaC is 17% of the exam." = 71 " Domain weights, cost, an 8-week plan, and the CloudFormation traps that cost marks." = 85 → 156. OK under 160. Good."

Chinese:
"DOP-C02 领域深度解析:配置管理与 IaC 占考试的 17%。权重、成本、学习计划,以及会让你丢分的 CloudFormation 陷阱。字符数:我估计约 170 个字符。太长了。精简为:“DOP-C02 深度解析:配置管理与 IaC 占考试的 17%。领域权重、成本、8 周计划,以及会让你丢分的 CloudFormation 陷阱。”粗略计算:“DOP-C02 深度解析:配置管理与 IaC 占考试的 17%。”= 71,“领域权重、成本、8 周计划,以及会让你丢分的 CloudFormation 陷阱。”= 85 → 156。好,低于 160。很好。"

Good.

Title: "DOP-C02 Exam Domain Deep Dive: Config Management & IaC Count chars: 54. Good." -> "DOP-C02 考试领域深度解析:配置管理与 IaC 字符数:54。很好。" Maybe "Count chars" is meta; yes.

Now content. Need include "Write it." -> "写出来。" maybe "开始写。"

"Section 1 TL;DR — 3 bullets." -> "第 1 节 TL;DR — 3 个要点。"

Then heading "## TL;DR" maybe keep. Could translate to "## TL;DR(摘要)" but "Keep section markers exactly" maybe keep. I'll keep "## TL;DR" to be safe as a marker. But content translated. Hmm heading text is English. However TL;DR is commonly left. Fine.

Bullets translate.

"Section 2:" -> "第 2 节:"

Then "## Who should sit this exam — and when to book something else" -> "## 谁应该参加这项考试——以及何时该报考其他考试"

"Then prose…" as above.

"## Six domains, six weights, and what they look like in practice" -> "## 六个领域、六种权重,以及它们在实践中的样子"

"Table." -> "表格。"

"Then prose: "Domain 2's task statements…" — From official exam guide, Domain 2 tasks:" -> "然后写正文:“领域 2 的任务陈述……”——来自官方考试指南,领域 2 的任务:"

Then list 2.1 etc. Translate:
2.1 Develop deployment automation using native AWS tools (CloudFormation, CDK, SAM, StackSets, Service Catalog, AppConfig, SSM documents) -> "2.1 使用原生 AWS 工具(CloudFormation、CDK、SAM、StackSets、Service Catalog、AppConfig、SSM 文档)开发部署自动化"
2.2 Create and manage cloud environments (Config, tag policies, license management) -> "2.2 创建和管理云环境(Config、标签策略、许可证管理)"
2.3 Automate configuration management (SSM State Manager, AppConfig, parameter store/secrets manager, Golden AMIs, Image Builder) -> "2.3 自动化配置管理(SSM State Manager、AppConfig、Parameter Store/Secrets Manager、黄金 AMI、Image Builder)"

"That's roughly right for DOP-C02 Domain 2. Good." -> "这大致符合 DOP-C02 领域 2。很好。"

"Section 3: ## Booking, cost, and what the 180 minutes feel like. Table + study plan sub? I planned to merge study plan. Let me split differently:" -> "第 3 节:## 预约、费用,以及 180 分钟是什么感觉。表格 + 学习计划子节?我原本计划合并学习计划。让我换一种拆分方式:"

"3. ## Booking, cost, and the study plan that fits around a full-time job" -> "3. ## 预约、费用,以及适合全职工作的学习计划"

"Two tables in one section is fine but need narrative separation." -> "一节里放两张表没问题,但需要用叙述分隔。"

"4. ## Where the Configuration Management and IaC questions bite" -> "4. ## 配置管理与 IaC 题目在哪里设坑"

"5. ## Exam technique" -> "5. ## 考试技巧"
"6. ## Sources" -> "6. ## 来源"

"That's 6 H2 + TL;DR = 6 total (TL;DR, who, domains, booking+study, traps+incident, technique, sources) = 7. Good." -> "这样是 6 个 H2 + TL;DR = 总共 6 个(TL;DR、谁、领域、预约+学习、陷阱+事件、技巧、来源)= 7。很好。" Wait count: 6 H2 + TL;DR = 7 actually. The text says "6 total" but lists 7. It's author's note. Translate exactly: "这样是 6 个 H2 + TL;DR = 总共 6 个(TL;DR、谁、领域、预约+学习、陷阱+事件、技巧、来源)= 7。很好。" That's contradictory but preserve. Maybe "That's 6 H2 + TL;DR = 6 total" -> "那是 6 个 H2 + TL;DR = 总共 6 个" Keep. Then list.

"Now write with attention to sentence variety and concrete details." -> "现在开始写,注意句式变化和具体细节。"

"Let me write it out fully." -> "让我完整写出来。"

"For the study plan table, it's a table with weeks. Fine." -> "学习计划表是一张按周排列的表格。没问题。"

"Let me write." -> "我来写。"

Then "—" keep.

"Section 4 content detail:" -> "第 4 节内容细节:"

"Prose intro: The exam guide's Domain 2 has three task areas… In practice the questions fall into five shapes…" -> "正文引言:考试指南的领域 2 有三个任务领域……在实践中,题目分为五种形态……"

"Traps list (real steps/comparisons allowed for lists):" -> "陷阱清单(列表可以包含真实步骤/对比):"

Bullets:

Then "Then "### When NOT to use a stack set" — hmm, requirement: "when NOT to use this" section. I already have "who should skip the exam" which is a when-not. I'll title section 2's subheading accordingly and also add a short "when not" for StackSets. Actually, I'll explicitly make a ### under section 4: "### When not to use StackSets for this" — brief: if you deploy to 3 accounts in one region and need per-account parameter differences, a pipeline looping aws cloudformation deploy --profile is simpler and easier to debug than StackSets, which fails whole operations on concurrency and gives you poor per-instance output. Good, concrete."

Translate meta:
"然后“### 何时不要使用 StackSet”——嗯,要求是:要有一个“何时不要使用这个”的部分。我已经有“谁应该跳过这项考试”,这正是一个“何时不要”。我会相应地给第 2 节的子标题命名,并且也为 StackSets 加一个简短的“何时不要”。实际上,我会在第 4 节下明确做一个 ###:“### 何时不要为此使用 StackSets”——简短说明:如果你在一个区域部署到 3 个账户,并且需要按账户设置不同参数,那么一个循环执行 aws cloudformation deploy --profile 的流水线比 StackSets 更简单、更容易调试,因为 StackSets 会因并发而让整个操作失败,并且每个实例的输出很差。好,具体。"

Then "Now the incident subsection." -> "现在写事件小节。"

"### The 02:14 rollback deadlock on prod-network" -> "### prod-network 上 02:14 的回滚死锁"

Prose:
"On 2026-02-11 I pushed a change set to prod-network (us-east-1, 61 resources) at 01:58 UTC… A route table had been edited in the console three weeks earlier… The update replaced a subnet, which changed the route table association; the route table resource had a manually added route that CloudFormation didn't know about… hmm, actually if the console changed it, CFN would just overwrite. Better: the failure was DELETE_FAILED on a resource because a security group was still in use… classic: "resource is in use" → rollback fails."

Translate:
"2026-02-11,我在 01:58 UTC 向 prod-network(us-east-1,61 个资源)推送了一个更改集……三周前有人在控制台编辑过一张路由表……这次更新替换了一个子网,从而改变了路由表关联;该路由表资源有一条手动添加的路由,CloudFormation 并不知道……嗯,实际上如果控制台改了它,CFN 只会覆盖掉。更好的版本是:失败原因是某个资源出现 DELETE_FAILED,因为一个安全组仍在使用中……经典情况:“资源正在使用中”→ 回滚失败。"

"Simpler realistic chain: The change set replaced an EC2 instance type (m5.large →