[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article:aws-japan":3},{"meta":4,"markdown":79,"quiz":80},{"type":5,"articleId":6,"slug":7,"title":8,"titleEn":9,"category":10,"summary":11,"publishedAt":12,"image":13,"vocabulary":14,"quizId":78},"article","exam-aws-japan","aws-japan","AWS認定 — 日本語受験のコツ","AWS Certification — Tips for Taking the Exam in Japanese","exams","A practitioner-oriented guide to taking AWS certification exams in Japanese.\nCovers the four-tier structure (Foundational \u002F Associate \u002F Professional \u002F\nSpecialty), the translation-quality issues that surface in the Japanese\nversion, the AWS-specific Japanese vocabulary you need to internalize, and\nrecommended cert paths for engineers planning to work in Japan.\n","2026-04-27T00:00:00Z","https:\u002F\u002Fimages.yamiyomi.com\u002Fexam-aws-japan.png",[15,20,25,29,34,38,42,46,50,54,58,62,66,70,74],{"word":16,"reading":17,"meaning":18,"level":19},"認定","にんてい","certification","N1",{"word":21,"reading":22,"meaning":23,"level":24},"試験","しけん","examination","N4",{"word":26,"reading":27,"meaning":28,"level":19},"仮想","かそう","virtual",{"word":30,"reading":31,"meaning":32,"level":33},"領域","りょういき","area \u002F region","N2",{"word":35,"reading":36,"meaning":37,"level":19},"利用可能領域","りようかのうりょういき","availability zone",{"word":39,"reading":40,"meaning":41,"level":19},"冗長","じょうちょう","redundant",{"word":43,"reading":44,"meaning":45,"level":19},"可用性","かようせい","availability",{"word":47,"reading":48,"meaning":49,"level":19},"耐障害性","たいしょうがいせい","fault tolerance",{"word":51,"reading":52,"meaning":53,"level":19},"暗号化","あんごうか","encryption",{"word":55,"reading":56,"meaning":57,"level":19},"復号化","ふくごうか","decryption",{"word":59,"reading":60,"meaning":61,"level":19},"認証","にんしょう","authentication",{"word":63,"reading":64,"meaning":65,"level":19},"認可","にんか","authorization",{"word":67,"reading":68,"meaning":69,"level":19},"監査","かんさ","audit",{"word":71,"reading":72,"meaning":73,"level":19},"翻訳品質","ほんやくひんしつ","translation quality",{"word":75,"reading":76,"meaning":77,"level":33},"直訳","ちょくやく","literal translation","exam-aws-japan-quiz","\n::heading\n[日本]{にほん::N5}で[働]{はたら::N3}くなら[AWS認定]{えーだぶりゅーえすにんてい::N3}は[ほぼ必須]{ほぼひっす::N1}\n\n#en\nFor working in Japan, AWS certifications are nearly mandatory\n::\n\n::para\n[日本]{にほん:Japan:N5}の[クラウド市場]{くらうどしじょう:cloud market:N3}は[AWS]{えーだぶりゅーえす:AWS}・[Azure]{あじゅーる}・[Google Cloud]{ぐーぐるくらうど}の[三強体制]{さんきょうたいせい:three-strong system:N3}とされ、[特]{とく::N4}に[エンタープライズ領域]{えんたーぷらいずりょういき:enterprise domain:N2}では[AWS]{えーだぶりゅーえす}の[シェア]{しぇあ:share}が[最]{もっと::N3}も[高]{たか::N5}いと[言]{い::N4}われています。[転職市場]{てんしょくしじょう:job market:N3}でも[AWS認定]{えーだぶりゅーえすにんてい:AWS certification:N3}を[歓迎条件]{かんげいじょうけん:preferred condition:N1}に[挙]{あ::N1}げる[企業]{きぎょう:companies:N1}が[多]{おお::N4}く、[Solutions Architect Associate]{そりゅーしょんずあーきてくとあそしえいと:SAA}の[取得]{しゅとく:acquisition:N3}を[最初]{さいしょ:first:N3}の[ハードル]{はーどる:hurdle}とする[ケース]{けーす:case}が[一般的]{いっぱんてき:common:N2}と[考]{かんが::N4}えられます。\n\n#en\nJapan's cloud market is generally described as a three-strong system of AWS, Azure, and Google Cloud, with AWS having the largest share in enterprise. Many companies list AWS certification as a preferred hiring condition, and treating Solutions Architect Associate (SAA) as the first hurdle is generally common.\n::\n\n::para\n[本記事]{ほんきじ:this article:N3}では[AWS認定試験]{えーだぶりゅーえすにんていしけん:AWS certification exams:N3}を[日本語]{にほんご:Japanese:N5}で[受験]{じゅけん:take an exam:N3}する[際]{さい::N3}の[実務的]{じつむてき:practical:N3}な[コツ]{こつ:tips}を[整理]{せいり:organize:N1}します。[試験体系]{しけんたいけい:exam system:N1}・[翻訳品質]{ほんやくひんしつ:translation quality:N1}・[頻出日本語]{ひんしゅつにほんご:frequent Japanese terms:N1}・[エンジニア]{えんじにあ:engineer}[向]{む::N3}けの[認定パス]{にんていぱす:certification path:N3}の[四点]{よんてん:four points:N3}に[絞]{しぼ::N1}って[紹介]{しょうかい:introduce:N2}します。\n\n#en\nThis article organizes practical tips for taking AWS certification exams in Japanese. It focuses on four points: the exam system, translation quality, frequent Japanese terminology, and recommended cert paths for engineers.\n::\n\n::heading\n[AWS認定]{えーだぶりゅーえすにんてい::N3}の[四階層]{よんかいそう::N2}\n\n#en\nThe four tiers of AWS certification\n::\n\n::para\n[AWS認定]{えーだぶりゅーえすにんてい::N3}は[公式]{こうしき:officially:N3}に[四つ]{よっつ:four:N5}の[階層]{かいそう:tiers:N2}で[整理]{せいり:organized:N1}されています。[基礎レベル]{きそれべる:Foundational level:N1}の[Cloud Practitioner]{くらうどぷらくてぃしょなー:CLF}、[アソシエイトレベル]{あそしえいとれべる:Associate level}（[SAA]{えすえーえー}・[DVA]{でぃーぶいえー}・[SOA]{えすおーえー}など）、[プロフェッショナルレベル]{ぷろふぇっしょなるれべる:Professional level}（[SAP]{えすえーぴー}・[DOP]{でぃーおーぴー}）、そして[専門知識]{せんもんちしき:Specialty:N2}（[SCS]{えすしーえす}・[ANS]{えーえぬえす}・[MLS]{えむえるえす}など）です。[受験順序]{じゅけんじゅんじょ:exam order:N1}に[厳密]{げんみつ:strict:N1}な[制約]{せいやく:constraint:N3}はないものの、[基礎]{きそ:foundation:N1}→[アソシエイト]{あそしえいと}→[プロ]{ぷろ}と[段階的]{だんかいてき:stepwise:N2}に[進]{すす::N3}むのが[安全]{あんぜん:safe:N3}とされています。\n\n#en\nAWS certification is officially organized into four tiers: Foundational (Cloud Practitioner \u002F CLF), Associate (SAA, DVA, SOA, etc.), Professional (SAP, DOP), and Specialty (SCS, ANS, MLS, etc.). There are no strict prerequisites between tiers, but progressing stepwise from Foundational → Associate → Professional is generally considered safe.\n::\n\n::callout\n[2026年時点]{にせんにじゅうろくねんじてん:as of 2026:N3}の[主要認定]{しゅようにんてい:main certifications:N3}：\n- [基礎]{きそ:Foundational:N1}：CLF (Cloud Practitioner) \u002F AIF (AI Practitioner)\n- [Associate]{あそしえいと}：SAA, DVA, SOA, MLA, DEA\n- [Professional]{ぷろふぇっしょなる}：SAP (Solutions Architect Pro), DOP (DevOps Engineer Pro)\n- [Specialty]{すぺしゃるてぃ}：SCS (Security), ANS (Networking), MLS (Machine Learning)\n\n#en\nAs of 2026, main certs include: Foundational (CLF, AIF); Associate (SAA, DVA, SOA, MLA, DEA); Professional (SAP, DOP); Specialty (SCS, ANS, MLS).\n::\n\n::heading\n[日本語版]{にほんごばん::N2}と[英語版]{えいごばん::N2}の[違]{ちが::N3}い\n\n#en\nDifferences between the Japanese and English versions\n::\n\n::para\n[AWS認定試験]{えーだぶりゅーえすにんていしけん::N3}は[日本語版]{にほんごばん:Japanese version:N2}と[英語版]{えいごばん:English version:N2}を[受験時]{じゅけんじ:at exam time:N3}に[切]{き::N4}り[替]{か::N2}えられます。[日本語版]{にほんごばん::N2}は[機械翻訳]{きかいほんやく:machine translation:N1}＋[人手校正]{ひとでこうせい:human review:N4}で[作成]{さくせい:created:N3}されているとされ、[特殊]{とくしゅ:specialized:N1}な[用語]{ようご:terms:N4}や[長]{なが::N5}い[シナリオ問題]{しなりおもんだい:scenario questions:N4}では[直訳]{ちょくやく:literal translation:N1}による[ぎこちなさ]{:awkwardness}が[残]{のこ::N3}る[ケース]{けーす:cases}があると[受験者]{じゅけんしゃ:test takers:N3}から[報告]{ほうこく:reported:N3}されています。\n\n#en\nYou can switch between Japanese and English versions at exam time. The Japanese version is reportedly created via machine translation + human review, and test takers report that awkwardness from literal translation can remain in specialized terms or long scenario questions.\n::\n\n::callout\n[日本語受験]{にほんごじゅけん::N3}で[よくある]{:common}[つまずき]{:stumbling points}：\n- [専門用語]{せんもんようご:specialized terms:N2}が[英語そのまま]{えいごそのまま:left in English:N4}か[直訳]{ちょくやく:literal:N1}か[揺]{ゆ::N1}れる\n- [問題文]{もんだいぶん:question text:N4}が[「〜してください」]{:please...}の[羅列]{られつ:enumeration:N1}で[長]{なが::N5}くなる\n- [選択肢]{せんたくし:options:N1}が[類似表現]{るいじひょうげん:similar expressions:N3}になり[区別]{くべつ:distinction:N2}しにくい\n- [サービス名]{さーびすめい:service names:N5}は[英語表記]{えいごひょうき:English notation:N3}のまま[残]{のこ::N3}る\n\n#en\nCommon stumbling points for Japanese-version takers: terminology wavers between English and literal translation; question text gets long with strings of \"please...\"; options use similar phrasings hard to distinguish; service names stay in English.\n::\n\n::heading\n[「英語切替]{えいごきりかえ::N2}」を[活用]{かつよう::N3}する\n\n#en\nUsing the \"English toggle\"\n::\n\n::para\n[試験中]{しけんちゅう:during the exam:N4}、[各設問]{かくせつもん:each question:N2}の[「言語切替]{げんごきりかえ:language switch:N2}」ボタンで[英語版]{えいごばん:English version:N2}を[即座]{そくざ:immediately:N1}に[表示]{ひょうじ:display:N3}できます。[日本語訳]{にほんごやく:Japanese translation:N1}が[不自然]{ふしぜん:unnatural:N3}に[感]{かん::N3}じた[時]{とき::N5}や、[専門用語]{せんもんようご:specialized terms:N2}の[原語]{げんご:original:N3}を[確認]{かくにん:confirm:N3}したい[時]{とき::N5}に[活用]{かつよう:utilize:N3}すべきとされます。[英語力]{えいごりょく:English ability:N4}に[自信]{じしん:confidence:N3}がある[受験者]{じゅけんしゃ:test takers:N3}ほど、[最終確認]{さいしゅうかくにん:final check:N3}に[英語版]{えいごばん::N2}を[併用]{へいよう:use in tandem:N1}する[傾向]{けいこう:tendency:N2}があると[言]{い::N4}われています。\n\n#en\nDuring the exam, the \"language switch\" button on each question can immediately display the English version. It is generally considered useful when the Japanese translation feels unnatural or when you want to confirm the original specialized term. Test takers more confident in English are said to tend to use the English version in tandem for final verification.\n::\n\n::heading\n[頻出AWS日本語]{ひんしゅつえーだぶりゅーえすにほんご::N1}カタログ\n\n#en\nFrequent AWS Japanese terminology catalog\n::\n\n::para\n[日本語版]{にほんごばん::N2}で[頻出]{ひんしゅつ:frequently appearing:N1}する[AWS]{えーだぶりゅーえす}[専門用語]{せんもんようご:specialized terms:N2}は[英語名]{えいごめい:English names:N4}と[併]{あわ::N1}せて[覚]{おぼ::N3}えておくと、[本番]{ほんばん:exam day:N3}の[読解速度]{どっかいそくど:reading speed:N3}が[大]{おお::N5}きく[向上]{こうじょう:improve:N3}すると[期待]{きたい:expect:N3}できます。[次]{つぎ::N3}の[一覧]{いちらん:list:N1}は[頻出]{ひんしゅつ::N1}の[基本用語]{きほんようご:basic terms:N1}を[インフラ]{いんふら:infrastructure}・[セキュリティ]{せきゅりてぃ:security}・[ストレージ]{すとれーじ:storage}・[ネットワーク]{ねっとわーく:network}に[分]{わ::N5}けたものです。\n\n#en\nFor frequent specialized AWS terms in the Japanese version, memorizing them paired with their English names can be expected to greatly improve reading speed on exam day. The following list groups basic terms into infrastructure, security, storage, and network.\n::\n\n::callout\n[インフラ]{いんふら}[基本]{きほん::N1}：\n- リージョン → [地域]{ちいき:region:N2}（[文中]{ぶんちゅう:in text:N4}は[「リージョン」]{りーじょん}のまま[多用]{たよう:often used:N4}）\n- アベイラビリティーゾーン → [利用可能領域]{りようかのうりょういき::N2} (AZ)\n- [仮想プライベートクラウド]{かそうぷらいべーとくらうど::N1} → VPC\n- [仮想]{かそう:virtual:N1}マシン → EC2 [インスタンス]{いんすたんす:instance}\n- [自動拡張]{じどうかくちょう:auto scaling:N1} → Auto Scaling\n- [負荷分散]{ふかぶんさん:load balancing:N2} → ELB \u002F ALB \u002F NLB\n\n#en\nInfrastructure: region (often left as リージョン), Availability Zone → 利用可能領域 (AZ), Virtual Private Cloud → VPC, virtual machine → EC2 instance, auto scaling → Auto Scaling, load balancing → ELB\u002FALB\u002FNLB.\n::\n\n::callout\n[セキュリティ]{せきゅりてぃ}[基本]{きほん::N1}：\n- [認証]{にんしょう::N1} → Authentication\n- [認可]{にんか::N3} → Authorization\n- [暗号化]{あんごうか::N3} → Encryption（[保存時]{ほぞんじ:at rest:N1}・[転送時]{てんそうじ:in transit:N4}）\n- [鍵管理]{かぎかんり:key management:N1} → KMS \u002F CloudHSM\n- [最小権限]{さいしょうけんげん:least privilege:N3} → Least Privilege\n- [監査ログ]{かんさろぐ:audit logs:N1} → CloudTrail\n\n#en\nSecurity: authentication → 認証, authorization → 認可, encryption → 暗号化 (at rest \u002F in transit), key management → KMS\u002FCloudHSM, least privilege → 最小権限, audit logs → CloudTrail.\n::\n\n::callout\n[ストレージ・DB]{すとれーじでぃーびー}[基本]{きほん::N1}：\n- [オブジェクトストレージ]{おぶじぇくとすとれーじ} → S3\n- [ブロックストレージ]{ぶろっくすとれーじ} → EBS\n- [ファイルストレージ]{ふぁいるすとれーじ} → EFS \u002F FSx\n- [リレーショナルデータベース]{りれーしょなるでーたべーす} → RDS\n- [非リレーショナル]{ひりれーしょなる:NoSQL:N3} → DynamoDB\n- [データウェアハウス]{でーたうぇあはうす} → Redshift\n- [冗長化]{じょうちょうか:redundancy:N1} → Multi-AZ \u002F [リードレプリカ]{りーどれぷりか:read replica}\n\n#en\nStorage\u002FDB: object storage → S3, block → EBS, file → EFS\u002FFSx, RDB → RDS, NoSQL → DynamoDB, data warehouse → Redshift, redundancy → Multi-AZ \u002F read replica.\n::\n\n::callout\n[ネットワーク]{ねっとわーく}[基本]{きほん::N1}：\n- [サブネット]{さぶねっと} → Subnet（[パブリック\u002Fプライベート]{ぱぶりっくぷらいべーと}）\n- [ルートテーブル]{るーとてーぶる} → Route Table\n- [インターネットゲートウェイ]{いんたーねっとげーとうぇい} → IGW\n- [NATゲートウェイ]{なっとげーとうぇい} → NAT Gateway\n- [セキュリティグループ]{せきゅりてぃぐるーぷ} → Security Group\n- [ネットワークACL]{ねっとわーくえーしーえる} → NACL\n\n#en\nNetwork: subnet (public\u002Fprivate), route table, Internet Gateway (IGW), NAT Gateway, Security Group, Network ACL (NACL).\n::\n\n::heading\n[Solutions Architect Associate]{そりゅーしょんずあーきてくとあそしえいと}の[攻略]{こうりゃく::N1}\n\n#en\nStrategy for Solutions Architect Associate\n::\n\n::para\n[Solutions Architect Associate]{そりゅーしょんずあーきてくとあそしえいと} (SAA) は[最]{もっと::N3}も[受験者数]{じゅけんしゃすう:test taker count:N3}が[多]{おお::N4}い[認定]{にんてい:certification:N3}とされ、[日本企業]{にほんきぎょう:Japanese companies:N1}での[評価]{ひょうか:evaluation:N1}も[高]{たか::N5}いです。[出題範囲]{しゅつだいはんい:exam scope:N1}は[「設計のベストプラクティス]{せっけいのべすとぷらくてぃす:design best practices:N2}」が[中心]{ちゅうしん:center:N4}で、[Well-Architected Framework]{うぇるあーきてくてっどふれーむわーく}の[6本柱]{ろくほんばしら:six pillars:N2}（[運用上の優秀性]{うんようじょうのゆうしゅうせい:operational excellence:N1}・[セキュリティ]{せきゅりてぃ}・[信頼性]{しんらいせい:reliability:N3}・[パフォーマンス効率]{ぱふぉーまんすこうりつ:performance efficiency:N1}・[コスト最適化]{こすとさいてきか:cost optimization:N3}・[持続可能性]{じぞくかのうせい:sustainability:N3}）が[出題基盤]{しゅつだいきばん:exam foundation:N1}になっています。\n\n#en\nSolutions Architect Associate (SAA) is generally said to have the highest test-taker count and high evaluation in Japanese companies. The scope centers on design best practices, with the six pillars of the Well-Architected Framework (operational excellence, security, reliability, performance efficiency, cost optimization, sustainability) as the exam foundation.\n::\n\n::callout\nSAA[頻出シナリオ]{ひんしゅつしなりお:frequent scenarios:N1}：\n- [可用性向上]{かようせいこうじょう:availability improvement:N3}：[Multi-AZ配置]{まるちえーぜっとはいち:multi-AZ placement:N3}・[Auto Scaling]{おーとすけーりんぐ}\n- [コスト削減]{こすとさくげん:cost reduction:N1}：[S3ライフサイクル]{えすすりーらいふさいくる:S3 lifecycle}・[Reserved Instance]{りざーぶどいんすたんす}\n- [災害対策]{さいがいたいさく:disaster recovery:N1}：[クロスリージョンレプリケーション]{くろすりーじょんれぷりけーしょん}\n- [大量アクセス]{たいりょうあくせす:heavy traffic:N2}：[CloudFront]{くらうどふろんと}＋[ALB]{えーえるびー}＋[Auto Scaling]{おーとすけーりんぐ}\n- [機密データ]{きみつでーた:confidential data:N1}：[KMS暗号化]{けーえむえすあんごうか:KMS encryption:N3}＋[VPCエンドポイント]{ぶいぴーしーえんどぽいんと}\n\n#en\nFrequent SAA scenarios: availability via Multi-AZ + Auto Scaling; cost reduction via S3 lifecycle + Reserved Instances; DR via cross-region replication; heavy traffic via CloudFront + ALB + Auto Scaling; confidential data via KMS encryption + VPC endpoints.\n::\n\n::heading\n[エンジニア向]{えんじにあむ::N3}けの[推奨]{すいしょう::N1}[認定パス]{にんていぱす::N3}\n\n#en\nRecommended certification paths for engineers\n::\n\n::para\n[在日エンジニア]{ざいにちえんじにあ:engineers in Japan:N3}が[キャリア]{きゃりあ:career}を[築]{きず::N2}く[際]{さい::N3}の[一例]{いちれい:one example:N3}として、[次]{つぎ::N3}の[3パターン]{さんぱたーん:three patterns}が[考]{かんが::N4}えられます。[実務経験]{じつむけいけん:practical experience:N3}と[組]{く::N3}み[合]{あ::N3}わせると[認定]{にんてい:certification:N3}の[価値]{かち:value:N1}が[最大化]{さいだいか:maximized:N3}されると[されています]{:said}。\n\n#en\nFor engineers building a career in Japan, the following three patterns are example paths. Combining them with practical experience is generally said to maximize the value of certifications.\n::\n\n::callout\n[インフラ系]{いんふらけい:infrastructure:N1}：\n- CLF → SAA → SOA → SAP → ANS or SCS\n\n[開発系]{かいはつけい:dev:N1}：\n- CLF → SAA → DVA → DOP → MLS or DEA\n\n[セキュリティ系]{せきゅりてぃけい:security:N1}：\n- CLF → SAA → SCS → SAP → ANS\n\n#en\nInfra path: CLF → SAA → SOA → SAP → ANS or SCS. Dev path: CLF → SAA → DVA → DOP → MLS or DEA. Security path: CLF → SAA → SCS → SAP → ANS.\n::\n\n::heading\n[受験]{じゅけん::N3}の[実務]{じつむ::N3}[Tips]{てぃっぷす}\n\n#en\nPractical tips for taking the exam\n::\n\n::para\n[AWS認定試験]{えーだぶりゅーえすにんていしけん::N3}は[ピアソンVUE]{ぴあそんぶいゆーいー}または[PSI]{ぴーえすあい}の[テストセンター]{てすとせんたー:test centers}か[オンライン受験]{おんらいんじゅけん:online proctoring:N3}が[選択]{せんたく:choice:N1}できます。[日本国内]{にほんこくない:domestic:N3}での[受験]{じゅけん::N3}は[東京]{とうきょう:Tokyo:N4}・[大阪]{おおさか:Osaka:N2}・[名古屋]{なごや:Nagoya:N4}を[中心]{ちゅうしん:center:N4}に[多数]{たすう:many:N3}の[会場]{かいじょう:venues:N4}があり、[平日午前]{へいじつごぜん:weekday morning:N3}は[空]{あ::N4}き[枠]{わく:slots:N1}が[多]{おお::N4}い[傾向]{けいこう:tendency:N2}とされます。\n\n#en\nAWS exams can be taken at Pearson VUE \u002F PSI test centers or via online proctoring. In Japan, there are many venues centered on Tokyo, Osaka, and Nagoya, with weekday mornings tending to have more open slots.\n::\n\n::callout\n[オンライン受験]{おんらいんじゅけん::N3}の[注意点]{ちゅういてん:cautions:N3}：\n- [机上]{きじょう:on the desk:N2}は[完全]{かんぜん:complete:N3}に[空]{から:empty:N4}にする[必要]{ひつよう::N3}あり\n- [時計]{とけい:watches:N4}・[飲料]{いんりょう:drinks:N4}・[紙]{かみ:paper:N4}は[原則]{げんそく:in principle:N2}[禁止]{きんし:prohibited:N2}\n- [日本語サポート]{にほんごさぽーと:Japanese support:N5}は[時間帯]{じかんたい:time slot:N2}によっては[英語]{えいご:English:N4}になる[ケース]{けーす:case}あり\n- [試験開始]{しけんかいし:start:N4}[30分前]{さんじゅっぷんまえ:30 min before:N5}に[チェックイン]{ちぇっくいん:check in}が[推奨]{すいしょう:recommended:N1}\n\n#en\nOnline proctoring cautions: desk must be completely empty; watches, drinks, paper are prohibited in principle; Japanese support may default to English depending on the time slot; checking in 30 min before start is recommended.\n::\n\n::heading\n[認定]{にんてい::N3}の[更新]{こうしん::N3}と[再受験]{さいじゅけん::N2}\n\n#en\nRecertification and retakes\n::\n\n::para\n[AWS認定]{えーだぶりゅーえすにんてい::N3}の[有効期間]{ゆうこうきかん:validity period:N2}は[原則]{げんそく:in principle:N2}[3年]{さんねん:3 years:N5}で、[期限切]{きげんぎ::N3}れ[前]{まえ::N5}に[同等]{どうとう:equivalent:N3}・[上位認定]{じょういにんてい:higher cert:N3}を[取得]{しゅとく:obtain:N3}するか、[専用]{せんよう:dedicated:N2}の[更新試験]{こうしんしけん:recertification exam:N3}を[受]{う::N3}けると[更新]{こうしん:renewed:N3}されると[されています]{:said}。[不合格]{ふごうかく:fail:N3}の[場合]{ばあい:case:N3}は[14日後]{じゅうよっかご:14 days later:N5}から[再受験]{さいじゅけん:retake:N2}が[可能]{かのう:possible:N3}で、[料金]{りょうきん:fee:N4}は[毎回発生]{まいかいはっせい:each time:N3}します。\n\n#en\nAWS certifications are generally valid for 3 years; before expiry, you can renew either by obtaining an equivalent or higher cert or by taking a dedicated recertification exam. If you fail, retaking is possible after 14 days, and the fee is incurred each time.\n::\n\n::callout\n[最後]{さいご::N3}に[本記事]{ほんきじ::N3}には[Solutions Architect Associate]{そりゅーしょんずあーきてくとあそしえいと}[相当]{そうとう::N3}の[6問]{ろくもん::N4}を[日本語]{にほんご::N5}で[用意]{ようい::N4}しました。[実際]{じっさい::N3}の[出題形式]{しゅつだいけいしき::N3}に[寄]{よ::N3}せたシナリオ[問題]{もんだい::N4}で[頻出語彙]{ひんしゅつごい::N1}と[判断]{はんだん:judgement:N3}を[確認]{かくにん::N3}してみてください。\n\n#en\nFinally, this article includes six SAA-level questions in Japanese. Use the scenario-style problems modeled on the actual exam format to check both frequent vocabulary and your decision-making.\n::\n",{"id":78,"title":81,"titleEn":82,"topicPath":10,"questions":83},"AWS認定（SAA相当）日本語確認テスト","AWS Certification (SAA-Level) Japanese Check Test",[84,110,130,152,174,198],{"id":85,"articleId":6,"question":86,"options":89,"correctLabel":95,"explanation":106,"tags":109},"exam-aws-japan-quiz-q01",{"en":87,"jp":88},"What is the most basic configuration to make a web application highly available?","[Web]{うぇぶ}アプリケーションを[高可用性]{こうかようせい:high availability}に[する]{:to make}ための[最]{もっと}も[基本的]{きほんてき:basic}な[構成]{こうせい:configuration}は？",[90,94,98,102],{"label":91,"jp":92,"en":93},"ア","[単一]{たんいつ}AZ[に]{}EC2[を]{}1[台配置]{はいち}","Place a single EC2 in one AZ",{"label":95,"jp":96,"en":97},"イ","[複数]{ふくすう:multiple}AZにEC2を[配置]{はいち}し[ELB]{いーえるびー}で[負荷分散]{ふかぶんさん:load balance}","Place EC2s across multiple AZs with ELB load balancing",{"label":99,"jp":100,"en":101},"ウ","[全]{すべて}のEC2を[同]{おな}じ[サブネット]{さぶねっと}に[集約]{しゅうやく:consolidate}","Consolidate all EC2 into the same subnet",{"label":103,"jp":104,"en":105},"エ","[CloudFront]{くらうどふろんと}[だけ]{:only}を[使用]{しよう}する","Use only CloudFront",{"en":107,"jp":108},"The basic high-availability pattern is generally Multi-AZ placement + ELB load balancing — a configuration that protects against single-AZ failures.","[高可用性]{こうかようせい}の[基本]{きほん}は[Multi-AZ]{まるちえーぜっと}[配置]{はいち}＋[ELB]{いーえるびー}による[負荷分散]{ふかぶんさん}とされ、[単一AZ]{たんいつえーぜっと}[障害]{しょうがい:fault}に[備]{そな}える[構成]{こうせい}です。",[45],{"id":111,"articleId":6,"question":112,"options":115,"correctLabel":99,"explanation":124,"tags":127},"exam-aws-japan-quiz-q02",{"en":113,"jp":114},"You want to retain access logs long-term while minimizing cost. The most appropriate service is?","[アクセスログ]{あくせすろぐ}を[長期保存]{ちょうきほぞん:long-term storage}し[コスト]{こすと}を[最小化]{さいしょうか:minimize}したい。[最]{もっと}も[適切]{てきせつ}な[サービス]{さーびす}は？",[116,118,120,122],{"label":91,"jp":117,"en":117},"EBS gp3",{"label":95,"jp":119,"en":119},"EFS Standard",{"label":99,"jp":121,"en":121},"S3 Glacier Deep Archive",{"label":103,"jp":123,"en":123},"DynamoDB",{"en":125,"jp":126},"S3 Glacier Deep Archive is generally said to be the lowest-cost storage class for archival use, suited to long-term retention.","S3 Glacier Deep Archive は[アーカイブ用途]{あーかいぶようと:archive use}で[最]{もっと}も[低コスト]{ていこすと}とされる[ストレージクラス]{すとれーじくらす}で、[長期保存]{ちょうきほぞん}に[適]{てき}しています。",[128,129],"cost-optimization","storage",{"id":131,"articleId":6,"question":132,"options":135,"correctLabel":95,"explanation":147,"tags":150},"exam-aws-japan-quiz-q03",{"en":133,"jp":134},"What is needed for outbound internet communication from a private subnet inside a VPC?","[VPC内]{ぶいぴーしーない}の[プライベート]{ぷらいべーと}サブネットから[インターネット]{いんたーねっと}に[アウトバウンド通信]{あうとばうんどつうしん:outbound communication}を[行]{おこな}いたい場合に必要なのは？",[136,139,142,144],{"label":91,"jp":137,"en":138},"[インターネットゲートウェイ]{いんたーねっとげーとうぇい}のみ","Internet Gateway only",{"label":95,"jp":140,"en":141},"NATゲートウェイ","NAT Gateway",{"label":99,"jp":143,"en":143},"Direct Connect",{"label":103,"jp":145,"en":146},"[追加設定]{ついかせってい}は[不要]{ふよう}","No additional setup needed",{"en":148,"jp":149},"When you want to allow outbound only from a private subnet, placing a NAT Gateway is generally common.","[プライベート]{ぷらいべーと}サブネットから[アウトバウンド]{あうとばうんど}のみを[許可]{きょか:allow}したい[場合]{ばあい}は[NATゲートウェイ]{なっとげーとうぇい}を[配置]{はいち}するのが[一般的]{いっぱんてき}とされます。",[151],"networking",{"id":153,"articleId":6,"question":154,"options":157,"correctLabel":95,"explanation":169,"tags":172},"exam-aws-japan-quiz-q04",{"en":155,"jp":156},"You want encryption at rest for S3 bucket data using keys managed by AWS. The simplest method is?","S3バケット内データの[保存時暗号化]{ほぞんじあんごうか:encryption at rest}を[AWS]{えーだぶりゅーえす}が[管理]{かんり}する[鍵]{かぎ}で[行]{おこな}いたい。最も簡易な方式は？",[158,161,163,166],{"label":91,"jp":159,"en":160},"[クライアント側暗号化]{くらいあんとがわあんごうか}","Client-side encryption",{"label":95,"jp":162,"en":162},"SSE-S3",{"label":99,"jp":164,"en":165},"[アプリケーション側]{あぷりけーしょんがわ}でAES-256","AES-256 in the application",{"label":103,"jp":167,"en":168},"[暗号化]{あんごうか}は[不要]{ふよう}","No encryption needed",{"en":170,"jp":171},"SSE-S3 is generally the simplest server-side encryption method using AWS-managed keys.","SSE-S3 は[AWS管理]{えーだぶりゅーえすかんり}の[鍵]{かぎ}で[サーバー側]{さーばーがわ:server-side}に[暗号化]{あんごうか}する[最]{もっと}も[簡易]{かんい:simple}な[方式]{ほうしき}とされます。",[173,53],"security",{"id":175,"articleId":6,"question":176,"options":179,"correctLabel":95,"explanation":192,"tags":195},"exam-aws-japan-quiz-q05",{"en":177,"jp":178},"What is effective for improving RDS read performance?","RDSの[読]{よ}み[込]{こ}みパフォーマンスを[向上]{こうじょう}させたい場合に有効な手段は？",[180,183,186,189],{"label":91,"jp":181,"en":182},"[Multi-AZ]{まるちえーぜっと}[配置]{はいち}","Multi-AZ placement",{"label":95,"jp":184,"en":185},"[リードレプリカ]{りーどれぷりか:read replica}を[追加]{ついか}","Add read replicas",{"label":99,"jp":187,"en":188},"[インスタンス]{いんすたんす}を[小]{ちい}さくする","Downsize the instance",{"label":103,"jp":190,"en":191},"[暗号化]{あんごうか}を[無効化]{むこうか:disable}","Disable encryption",{"en":193,"jp":194},"Multi-AZ's main purpose is availability; for read performance, adding read replicas is generally effective.","[Multi-AZ]{まるちえーぜっと}は[可用性向上]{かようせいこうじょう}が[主目的]{しゅもくてき:main purpose}で、[読]{よ}み[込]{こ}み[性能]{せいのう}には[リードレプリカ]{りーどれぷりか}の[追加]{ついか}が[有効]{ゆうこう}とされます。",[196,197],"database","performance",{"id":199,"articleId":6,"question":200,"options":203,"correctLabel":95,"explanation":216,"tags":219},"exam-aws-japan-quiz-q06",{"en":201,"jp":202},"What is the most practical tip for taking AWS certification in Japanese?","AWS認定試験を[日本語]{にほんご}で[受験]{じゅけん}する[際]{さい}の[最]{もっと}も[実用的]{じつようてき}な[コツ]{こつ}は？",[204,207,210,213],{"label":91,"jp":205,"en":206},"[英語]{えいご}を[一切見]{いっさいみ}ない","Never look at English",{"label":95,"jp":208,"en":209},"[不自然]{ふしぜん}な[訳文]{やくぶん}は[「言語切替]{げんごきりかえ}[」]{}で[英語版]{えいごばん}を[確認]{かくにん}する","Use the language toggle to check the English version when translation feels unnatural",{"label":99,"jp":211,"en":212},"[サービス名]{さーびすめい}を[全]{すべ}て[日本語化]{にほんごか}する","Translate all service names into Japanese",{"label":103,"jp":214,"en":215},"[問題文]{もんだいぶん}を[読]{よ}まずに[直感]{ちょっかん}で[答]{こた}える","Skip reading and answer by intuition",{"en":217,"jp":218},"Since the Japanese version is generally MT + human review with awkward phrasings remaining, using the language toggle to check English is a practical tip.","[日本語版]{にほんごばん}は[機械翻訳]{きかいほんやく}＋[人手校正]{ひとでこうせい}とされ、[不自然]{ふしぜん}な[訳]{やく}が[残]{のこ}る[ケース]{けーす}があるため[「言語切替]{げんごきりかえ}[」]{}での[英語版確認]{えいごばんかくにん}が[実用的]{じつようてき}な[コツ]{こつ}とされます。",[220],"exam-tips"]