【評判】KCSA: Kubernetes & Cloud Native Security Associate EXAM-PREP

レビュー数の推移

直近6か月以内に本講座のレビューに関して記載された記事はありません。

学習内容

詳細

本コースの特徴

本コースの特徴を単語単位でまとめました。以下の単語が気になる方は、ぜひ本講座の受講をオススメします。

受講者の感想

本講座を受講した皆さんの感想を以下にまとめます。

評価や口コミ

参考になる受講者の口コミやレビューを以下にまとめます。

• 悪い点

• ● all same questions and not holistic, need refund.Here’s a corrected and polished version of your feedback: "I did not expect repetitive questions in the practice tests, but unfortunately, several questions were repeated. Secondly, there are only two practice tests included—come on, only two tests for the price we paid? That's not worth it. There should be at least five practice tests with an increasing difficulty level to better prepare us for the exam."Poorly designed questions that seem intentionally confusingBought this course to prepare for the KCSA exam, but the question quality is honestly frustrating.Several obvious issues:Concepts are randomly connected to securityAsks how Scheduler improves security? Answer says through Node Affinity for pod scheduling. Come on, that's the Scheduler's basic function, what does it have to do with security?Asks how ReplicaSet prevents DoS? Says maintaining pod count can mitigate attacks. The logic makes no sense - ReplicaSet only manages pod count, spinning up more pods during a real attack would only make things worseSupply chain security question is way offOnly mentions image signing and scanning, completely ignores software dependency scanning, SBOM, license compliance - the actual core conceptsSupply chain security should focus on scanning for dependency vulnerabilities, risk assessment, licensing issues, etc. Their answer explanation only has a slight relation to real supply chain securityZero Trust explanation is wrongSimplifies Zero Trust to just network segmentation. Zero Trust's core principle is "never trust, always verify" - it's about identity verification and authorization. Network isolation is just one technique, not the main pointConfigMaps vs Secrets question misses the pointThe real issue is that ConfigMap data is completely plaintext - anyone can kubectl get configmap -o yaml and directly see passwords. Secrets aren't really secure either, just Base64 encoded. By default neither is encrypted, the only difference is one is completely exposed while the other has minimal obfuscationBut the question doesn't explain this core difference. Instead it just says "Kubernetes doesn't treat ConfigMaps as sensitive data". This completely misses the point. The issue isn't whether Kubernetes "recognizes" it - it's that the data has no protection! It's like asking why you shouldn't write passwords on sticky notes, and the answer being "because sticky notes aren't designed for privacy protection" - makes no senseDoS question is also weirdSays not setting resource limits leads to DoS attacks. Technically correct, but the terminology is imprecise. In practice it's more often misconfiguration or program bugs, not necessarily attacks. More accurate terms would be resource exhaustion or noisy neighbor problemConclusion:This question set is just for memorizing answers, don't expect to actually understand Kubernetes security. Questions are poorly designed, many seem made to confuse rather than educate, and explanations don't hold up to scrutiny.If you already bought it, use it to get familiar with question format, but don't take the explanations as gospel. For real learning, stick to official docs and hands-on practice.Giving 2 stars only because it at least covers exam topics, but quality is really lacking.I scored over 90% in these tests and 84% on the real exam. It's very good for learning but the questions on the real exam are different. It's not enough to learn the stuff covered by this set of questions and pass the exam but for sure it helps a lot.The actual exam questions are different and a lot harder than the questions in this course.A lot of the questions have the wrong answers set解説が欲しかったです。

レビューの一覧

　・KCSA受験レポート｜落ちても得られた3つの収穫[2025-08-21に投稿]

他にオススメな関連講座のランキング

• 　・kubernetesに関連するオススメの講座ランキング
• 　・KCSAに関連するオススメの講座ランキング