[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"quiz:tech-data-architecture-quiz":3,"quiz-article-index":158},{"quizId":4,"title":5,"titleEn":6,"topicPath":7,"questions":8},"tech-data-architecture-quiz","テック確認テスト — データ整合性とマルチテナント","Tech Check Quiz — Data Integrity and Multi-Tenancy","tech",[9,38,62,86,111,135],{"id":10,"articleId":11,"question":12,"options":15,"correctLabel":21,"explanation":32,"tags":35},"tech-data-architecture-quiz-q01","tech-freee-accounting",{"en":13,"jp":14},"Which is the most appropriate policy for guaranteeing double-entry bookkeeping integrity at freee?","freeeで複式簿記の整合性を担保するうえで、もっとも適切な方針はどれか。",[16,20,24,28],{"label":17,"jp":18,"en":19},"ア","夜間バッチで整合性を検証し、書き込み時は無検証で速度を優先する。","Verify integrity in nightly batches and prioritize speed by skipping write-time checks.",{"label":21,"jp":22,"en":23},"イ","書き込みトランザクション内で借方合計と貸方合計の一致をDB制約とアプリ層の両方で検証する。","Verify debit-credit equality at both DB constraint and application layer within the write transaction.",{"label":25,"jp":26,"en":27},"ウ","顧客に手動で残高を確認させ、不整合が出たら通知してもらう。","Have customers manually verify balances and report discrepancies.",{"label":29,"jp":30,"en":31},"エ","仕訳ごとにユニークIDを発行するだけで、合計検証は不要にする。","Issue a unique ID per journal entry and skip total verification.",{"en":33,"jp":34},"Integrity must always be verified at write time. Multi-layered defense across the app layer and DB constraint is basic; nightly batches are an additional fortress.","整合性は書き込み時に必ず検証することが鉄則。アプリ層とDB制約の多層防御が基本。夜間バッチは追加の砦として併用する。",[36,37],"accounting","integrity",{"id":39,"articleId":11,"question":40,"options":43,"correctLabel":21,"explanation":56,"tags":59},"tech-data-architecture-quiz-q02",{"en":41,"jp":42},"When the same transaction data arrives from a bank API multiple times, which approach does freee take to prevent double-posting?","銀行APIから同じ取引データが複数回送られてきた場合、二重計上を防ぐためにfreeeが採る手法はどれか。",[44,47,50,53],{"label":17,"jp":45,"en":46},"受信時刻でソートし、最新だけを採用する。","Sort by receive time and adopt only the latest.",{"label":21,"jp":48,"en":49},"外部システムの取引IDを冪等性キーとしてユニーク制約を掛ける。","Apply a unique constraint on the external transaction ID as an idempotency key.",{"label":25,"jp":51,"en":52},"金額が同じ取引はすべて自動的に削除する。","Automatically delete all transactions with the same amount.",{"label":29,"jp":54,"en":55},"重複は許容し、後でユーザーに削除させる。","Allow duplicates and have the user delete them later.",{"en":57,"jp":58},"Using the external system's transaction ID as a unique-constrained idempotency key ensures the result converges to one even if retries occur.","外部システムが発行する取引IDをユニーク制約付きの冪等性キーとして使うことで、再試行が起きても結果が一つに収束する。",[60,61],"idempotency","fintech",{"id":63,"articleId":11,"question":64,"options":67,"correctLabel":25,"explanation":80,"tags":83},"tech-data-architecture-quiz-q03",{"en":65,"jp":66},"Which is the correct design for an audit trail?","監査証跡として正しい設計はどれか。",[68,71,74,77],{"label":17,"jp":69,"en":70},"古い値を上書きし、最新の状態だけ保持する。","Overwrite old values and keep only the latest state.",{"label":21,"jp":72,"en":73},"削除時はレコード自体を物理削除する。","Physically delete the record itself on deletion.",{"label":25,"jp":75,"en":76},"追記専用のイベントログにすべての変更を不変な形で記録する。","Record all changes in immutable form to an append-only event log.",{"label":29,"jp":78,"en":79},"監査ログは一年で自動削除し、ストレージを節約する。","Auto-delete audit logs after one year to save storage.",{"en":81,"jp":82},"Rather than 'deleting data,' 'adding the fact of deletion' is the iron rule of accounting systems. Append-only logs are required so that who changed what and when can be fully reproduced.","「データを消す」のではなく「削除という事実を追加する」のが会計システムの鉄則。追記専用ログで誰がいつ何を変えたかを完全に再現できる必要がある。",[84,85],"audit","immutability",{"id":87,"articleId":88,"question":89,"options":92,"correctLabel":21,"explanation":105,"tags":108},"tech-data-architecture-quiz-q04","tech-mf-multitenant",{"en":90,"jp":91},"Which best describes Money Forward's multi-tenant isolation strategy?","Money Forwardが採るマルチテナント分離戦略の説明として最も適切なものはどれか。",[93,96,99,102],{"label":17,"jp":94,"en":95},"全顧客を必ず同じ行レベル分離で扱い、運用負荷を最小化する。","Always handle all customers with row-level isolation to minimize operational load.",{"label":21,"jp":97,"en":98},"プロダクト特性に応じて行レベル分離とスキーマ・専用クラスタ隔離を使い分ける。","Use row-level isolation and schema\u002Fdedicated-cluster isolation selectively per product characteristic.",{"label":25,"jp":100,"en":101},"セキュリティを最優先し、必ずテナントごとに別物理サーバを与える。","Always give each tenant a separate physical server, prioritizing security.",{"label":29,"jp":103,"en":104},"データ分離はアプリ層に任せ、DB側では一切制約を掛けない。","Leave isolation entirely to the app layer and apply no DB-side constraints.",{"en":106,"jp":107},"There is no silver bullet — both row-level and schema-level approaches are used selectively, and large customers are isolated to dedicated clusters.","銀の弾丸はなく、行レベルとスキーマレベルの両方を製品特性に応じて使い分け、大口顧客は専用クラスタへ隔離する。",[109,110],"multitenant","isolation",{"id":112,"articleId":88,"question":113,"options":116,"correctLabel":21,"explanation":129,"tags":132},"tech-data-architecture-quiz-q05",{"en":114,"jp":115},"Which design is required to safely handle multi-tenancy with shared caches (e.g. Redis)?","共有キャッシュ（Redisなど）でマルチテナントを安全に扱うために必要な設計はどれか。",[117,120,123,126],{"label":17,"jp":118,"en":119},"テナントIDをキーに含めず、すべてのテナントでキャッシュを共有する。","Omit tenant IDs from keys and share cache entries across all tenants.",{"label":21,"jp":121,"en":122},"すべてのキャッシュキーにテナントプレフィックスを強制し、ライブラリ層で誤用を防ぐ。","Enforce a tenant prefix on every cache key and prevent misuse at the library layer.",{"label":25,"jp":124,"en":125},"キャッシュは無効化し、すべて毎回DBから読む。","Disable caches and always read from the DB.",{"label":29,"jp":127,"en":128},"テナントごとに別Redisインスタンスを必ず立てる。","Always provision a separate Redis instance per tenant.",{"en":130,"jp":131},"Omitting tenant IDs from cache keys causes a fatal bug where other tenants' data is returned. Enforcing prefixes and library-layer guards is fundamental.","テナントIDをキーから外すと他テナントのデータが返る致命的バグが発生する。プレフィックス強制とライブラリ層のガードが基本。",[133,134],"cache","security",{"id":136,"articleId":88,"question":137,"options":140,"correctLabel":21,"explanation":153,"tags":156},"tech-data-architecture-quiz-q06",{"en":138,"jp":139},"Which is the most appropriate countermeasure for the 'noisy neighbor' problem?","「騒がしい隣人問題（noisy neighbor）」への対策として最も適切なのはどれか。",[141,144,147,150],{"label":17,"jp":142,"en":143},"全テナントに同じ性能を保証するため、負荷の高いテナントもそのまま放置する。","Leave high-load tenants alone since all tenants must get equal performance.",{"label":21,"jp":145,"en":146},"テナントごとのリクエストレート・同時接続数・CPU時間に上限を設ける。","Set per-tenant upper limits on request rate, concurrent connections, and CPU time.",{"label":25,"jp":148,"en":149},"問題が出たら手動で当該テナントを完全に停止する。","Manually stop the offending tenant entirely when problems arise.",{"label":29,"jp":151,"en":152},"アプリケーション層では何もせず、ハードウェアの増強だけで対応する。","Do nothing at the app layer and address it only by adding hardware.",{"en":154,"jp":155},"Setting per-tenant limits on request rate, concurrent connections, and CPU time prevents one tenant from pressuring overall performance. Extremely large customers are isolated to dedicated clusters.","リクエストレート・同時接続数・CPU時間に上限を設けることで一テナントが全体性能を圧迫することを防ぐ。極端に大きい顧客は専用クラスタへ隔離する。",[109,157],"resource-quota",{"culture-anime-studio-ghibli":159,"culture-bonsai-art":163,"tech-cybozu-kintone-no-code":167,"living-denki-gas-suidou":171,"tech-gree-mobile-game-ops":175,"culture-green-tea-types":179,"living-gym-fitness":183,"living-internet-hikari":187,"living-jisha-de-kau":191,"exam-jlpt-n3-grammar":195,"exam-jlpt-n3-vocab":199,"bj-job-gata-koyou":203,"culture-kabuki-noh-bunraku":207,"bj-karoushi-hatarakikata":211,"living-keitai-mobile-plan":215,"living-konbini-atm-banking":219,"living-kosodate-hoiku":223,"culture-nihon-teien":227,"bj-nomikai-survival":231,"tech-pixiv-image-cdn":235,"culture-sake-shochu":239,"bj-sankyu-ikukyu":243,"tech-sansan-eight-platform":247,"culture-shichi-go-san":251,"bj-shukatsu-shinsotsu":255,"tech-smartnews-recommendation":259,"bj-taishoku-todoke":263,"bj-telework-policy":267,"bj-tenshoku-resume":271,"tech-yahoo-japan-search":275,"culture-anime-business":279,"exam-ap":283,"exam-aws-japan":287,"law-chosakuken":291,"tech-cookpad-recipe-search":295,"tech-cybozu-kintone-api":299,"tech-dena-observability":303,"law-denshi-chouho":307,"tech-digital-cho-cloud":311,"exam-fe":315,"tech-freee-accounting":319,"law-furiransu-hou":322,"law-harassment":326,"tech-hatena-mackerel":330,"bj-hourensou":334,"bj-hyouka-mendan":338,"law-invoice":342,"exam-it-passport":346,"culture-izakaya":350,"culture-j-league":354,"culture-jinja-tera":358,"exam-jlpt-n1-dokkai":362,"exam-jlpt-n2-business":366,"bj-kaigi-manner":370,"living-kakutei-shinkoku":374,"bj-keigo-kihon":378,"law-keihin-hyouji":382,"living-kenkou-hoken":386,"living-kosei-nenkin":390,"tech-line-llmops":394,"tech-line-streaming":398,"living-chintai-keiyaku":402,"living-eijuken":406,"living-engineer-visa":410,"living-ginkou-koza":414,"living-hikkoshi-checklist":418,"living-koudo-senmon":422,"culture-matsuri":426,"bj-meishi-koukan":430,"tech-mercari-merpay-id":434,"tech-mercari-microservices":438,"tech-mf-multitenant":442,"bj-nemawashi-ringi":445,"living-nenmatsu-chousei":449,"bj-1on1":453,"bj-online-kaigi":457,"culture-onsen":461,"culture-pro-baseball":465,"culture-ramen":469,"tech-recruit-data-platform":473,"law-roukikihou-kihon":477,"culture-sado":481,"culture-sandou":485,"culture-seasonal-events":489,"exam-sg":493,"bj-shagai-mail":497,"bj-shanai-mail":501,"culture-sumo":505,"culture-sushi":509,"culture-washoku":513,"law-yuukyuu-kyuuka":517,"kjh-k1-h04-anzen-kanri":521,"bill-one-auth":525,"contract-one-vision":529,"kjh-k1-h04-daisan-sha-teikyou":533,"eight-web-renewal":537,"kjh-k1-h04-gaikoku-kiroku":541,"kjh-k2-h04-gijutsu-jisshi":545,"kjh-k2-h04-gijutsu-kiso":549,"kjh-k1-h01-hotaikei":553,"kjh-k1-h06-hoyu-data":557,"kjh-k1-h07-kamei-kakou":561,"kjh-k1-h05-kanren-joho":565,"kjh-k1-h02-kihon-rinen":569,"kjh-k1-h09-jikkousei":573,"kjh-k1-h10-gyousei":577,"kjh-k1-h11-my-number-hogo":581,"kjh-k1-h11-my-number-sousoku":585,"kjh-k2-h01-guideline":589,"kjh-k2-h01-security-kiso":593,"kjh-k2-h02-anzen-kanri-sochi":597,"kjh-k2-h02-soshiki-kiso":601,"kjh-k2-h03-office":605,"kjh-k1-h03-riyou-mokuteki":609,"sansan-data-intelligence":613,"sansan-engineer-team-infra":617,"sansan-honne-15":621,"sansan-interview-110":625,"sansan-interview-126":629,"sansan-interview-127":633,"sansan-interview-130":637,"sansan-interview-40":641,"sansan-oyaco":645,"kjh-k1-h03-tekisei-shutoku":649,"kjh-k1-h08-tokumei-kakou":653},{"articleId":160,"path":161,"title":162},"culture-anime-studio-ghibli","\u002Farticles\u002Fculture\u002Fanime-studio-ghibli","スタジオジブリ作品史 — 宮崎駿・高畑勲・鈴木敏夫が築いた40年",{"articleId":164,"path":165,"title":166},"culture-bonsai-art","\u002Farticles\u002Fculture\u002Fbonsai-art","盆栽の世界 — 小宇宙を育てる日本の芸術",{"articleId":168,"path":169,"title":170},"tech-cybozu-kintone-no-code","\u002Farticles\u002Ftech\u002Fcybozu-kintone-no-code","kintoneのローコード戦略 — 業務アプリを誰でも作れる仕組み",{"articleId":172,"path":173,"title":174},"living-denki-gas-suidou","\u002Farticles\u002Fliving-in-japan\u002Fdenki-gas-suidou","電気・ガス・水道の契約 — 引越し時のライフライン手続き",{"articleId":176,"path":177,"title":178},"tech-gree-mobile-game-ops","\u002Farticles\u002Ftech\u002Fgree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側",{"articleId":180,"path":181,"title":182},"culture-green-tea-types","\u002Farticles\u002Fculture\u002Fgreen-tea-types","日本茶の種類と淹れ方 — 煎茶・玉露・抹茶の違い",{"articleId":184,"path":185,"title":186},"living-gym-fitness","\u002Farticles\u002Fliving-in-japan\u002Fgym-fitness","ジムとフィットネスクラブ — 入会から解約までの実務ガイド",{"articleId":188,"path":189,"title":190},"living-internet-hikari","\u002Farticles\u002Fliving-in-japan\u002Finternet-hikari-keiyaku","光回線とネット契約 — フレッツ・NURO・auひかり比較",{"articleId":192,"path":193,"title":194},"living-jisha-de-kau","\u002Farticles\u002Fliving-in-japan\u002Fjisha-de-kau","日本で不動産を買う — 外国人でも住宅ローンを組む方法",{"articleId":196,"path":197,"title":198},"exam-jlpt-n3-grammar","\u002Farticles\u002Fexams\u002Fjlpt-n3-grammar","JLPT N3 文法 — 初級から中級への橋渡し",{"articleId":200,"path":201,"title":202},"exam-jlpt-n3-vocab","\u002Farticles\u002Fexams\u002Fjlpt-n3-vocab","JLPT N3 語彙対策 — 1500語をどう攻略するか",{"articleId":204,"path":205,"title":206},"bj-job-gata-koyou","\u002Farticles\u002Fbusiness-japanese\u002Fjob-gata-koyou","ジョブ型雇用への移行 — メンバーシップ型からの脱却",{"articleId":208,"path":209,"title":210},"culture-kabuki-noh-bunraku","\u002Farticles\u002Fculture\u002Fkabuki-noh-bunraku","歌舞伎・能・文楽 — 日本三大伝統演劇の世界",{"articleId":212,"path":213,"title":214},"bj-karoushi-hatarakikata","\u002Farticles\u002Fbusiness-japanese\u002Fkaroushi-hatarakikata","過労死と働き方改革 — 残業規制の歴史と現状",{"articleId":216,"path":217,"title":218},"living-keitai-mobile-plan","\u002Farticles\u002Fliving-in-japan\u002Fkeitai-mobile-plan","携帯電話契約の選び方 — 大手キャリア・MVNO・eSIM完全ガイド",{"articleId":220,"path":221,"title":222},"living-konbini-atm-banking","\u002Farticles\u002Fliving-in-japan\u002Fkonbini-atm-banking","コンビニATMと電子マネー — 現金とキャッシュレスのハイブリッド生活",{"articleId":224,"path":225,"title":226},"living-kosodate-hoiku","\u002Farticles\u002Fliving-in-japan\u002Fkosodate-hoiku","子育て支援と保育園 — 児童手当・保活・無償化制度",{"articleId":228,"path":229,"title":230},"culture-nihon-teien","\u002Farticles\u002Fculture\u002Fnihon-teien","日本庭園の世界 — 池泉・枯山水・露地の様式",{"articleId":232,"path":233,"title":234},"bj-nomikai-survival","\u002Farticles\u002Fbusiness-japanese\u002Fnomikai-survival","飲み会・ノミニケーション完全攻略 — 新人エンジニアのサバイバルガイド",{"articleId":236,"path":237,"title":238},"tech-pixiv-image-cdn","\u002Farticles\u002Ftech\u002Fpixiv-image-cdn","pixivの画像配信基盤 — 数億イラストを世界に届ける技術",{"articleId":240,"path":241,"title":242},"culture-sake-shochu","\u002Farticles\u002Fculture\u002Fsake-shochu","日本酒と焼酎入門 — 製法・産地・飲み方の基礎",{"articleId":244,"path":245,"title":246},"bj-sankyu-ikukyu","\u002Farticles\u002Fbusiness-japanese\u002Fsankyu-ikukyu","産休・育休制度の実務 — 取得スケジュールと給付金",{"articleId":248,"path":249,"title":250},"tech-sansan-eight-platform","\u002Farticles\u002Ftech\u002Fsansan-eight-platform","Eight 名刺SaaSの基盤進化 — モバイルから法人向けプラットフォームへ",{"articleId":252,"path":253,"title":254},"culture-shichi-go-san","\u002Farticles\u002Fculture\u002Fshichi-go-san","七五三 — 子供の成長を祝う伝統行事",{"articleId":256,"path":257,"title":258},"bj-shukatsu-shinsotsu","\u002Farticles\u002Fbusiness-japanese\u002Fshukatsu-shinsotsu","新卒就活の流れ — エントリーシートから内定まで",{"articleId":260,"path":261,"title":262},"tech-smartnews-recommendation","\u002Farticles\u002Ftech\u002Fsmartnews-recommendation","SmartNewsの推薦システム — ニュースを最適化する機械学習",{"articleId":264,"path":265,"title":266},"bj-taishoku-todoke","\u002Farticles\u002Fbusiness-japanese\u002Ftaishoku-todoke","退職届と退職願 — 違いと書き方、円満退職への手順",{"articleId":268,"path":269,"title":270},"bj-telework-policy","\u002Farticles\u002Fbusiness-japanese\u002Ftelework-policy","テレワーク制度の現状 — コロナ後の在宅勤務とハイブリッド",{"articleId":272,"path":273,"title":274},"bj-tenshoku-resume","\u002Farticles\u002Fbusiness-japanese\u002Ftenshoku-resume","転職活動の進め方 — 履歴書と職務経歴書の書き方",{"articleId":276,"path":277,"title":278},"tech-yahoo-japan-search","\u002Farticles\u002Ftech\u002Fyahoo-japan-search","Yahoo! JAPAN検索の基盤 — 日本語特化の大規模検索システム",{"articleId":280,"path":281,"title":282},"culture-anime-business","\u002Farticles\u002Fculture\u002Fanime-business","アニメ・漫画文化と産業構造 — グローバル展開の現状",{"articleId":284,"path":285,"title":286},"exam-ap","\u002Farticles\u002Fexams\u002Fap","応用情報技術者試験 — 重点出題分野",{"articleId":288,"path":289,"title":290},"exam-aws-japan","\u002Farticles\u002Fexams\u002Faws-japan","AWS認定 — 日本語受験のコツ",{"articleId":292,"path":293,"title":294},"law-chosakuken","\u002Farticles\u002Flaw\u002Fchosakuken","著作権法 — エンジニアが知っておくべき基礎",{"articleId":296,"path":297,"title":298},"tech-cookpad-recipe-search","\u002Farticles\u002Ftech\u002Fcookpad-recipe-search-ranking","Cookpadのレシピ検索 — 学習to-rank実装",{"articleId":300,"path":301,"title":302},"tech-cybozu-kintone-api","\u002Farticles\u002Ftech\u002Fcybozu-kintone-api-design","kintone API設計の十年 — 後方互換性との戦い",{"articleId":304,"path":305,"title":306},"tech-dena-observability","\u002Farticles\u002Ftech\u002Fdena-mobile-game-observability","DeNAのモバイルゲーム監視基盤",{"articleId":308,"path":309,"title":310},"law-denshi-chouho","\u002Farticles\u002Flaw\u002Fdenshi-chouho","電子帳簿保存法 — スキャナ保存と電子取引保存の対応",{"articleId":312,"path":313,"title":314},"tech-digital-cho-cloud","\u002Farticles\u002Ftech\u002Fdigital-cho-government-cloud","デジタル庁ガバメントクラウド技術詳細",{"articleId":316,"path":317,"title":318},"exam-fe","\u002Farticles\u002Fexams\u002Ffe","基本情報技術者試験 — シラバス全体像",{"articleId":11,"path":320,"title":321},"\u002Farticles\u002Ftech\u002Ffreee-accounting-integrity","freeeの会計データ整合性 — 仕訳バランスの自動検証",{"articleId":323,"path":324,"title":325},"law-furiransu-hou","\u002Farticles\u002Flaw\u002Ffuriransu-hou","フリーランス保護法（2024年施行）— 取引適正化のポイント",{"articleId":327,"path":328,"title":329},"law-harassment","\u002Farticles\u002Flaw\u002Fharassment","ハラスメント関連法 — パワハラ・セクハラ・マタハラ防止義務",{"articleId":331,"path":332,"title":333},"tech-hatena-mackerel","\u002Farticles\u002Ftech\u002Fhatena-mackerel-alert-design","MackerelのAlert設計思想",{"articleId":335,"path":336,"title":337},"bj-hourensou","\u002Farticles\u002Fbusiness-japanese\u002Fhourensou","報・連・相 — 日本企業のコミュニケーションの基本",{"articleId":339,"path":340,"title":341},"bj-hyouka-mendan","\u002Farticles\u002Fbusiness-japanese\u002Fhyouka-mendan","評価面談の準備と振り返り",{"articleId":343,"path":344,"title":345},"law-invoice","\u002Farticles\u002Flaw\u002Finvoice-seido","インボイス制度の仕組みと実務 — 適格請求書発行事業者",{"articleId":347,"path":348,"title":349},"exam-it-passport","\u002Farticles\u002Fexams\u002Fit-passport","ITパスポート試験 — 概要と学習法",{"articleId":351,"path":352,"title":353},"culture-izakaya","\u002Farticles\u002Fculture\u002Fizakaya","居酒屋文化と乾杯のマナー — お通しから締めまで",{"articleId":355,"path":356,"title":357},"culture-j-league","\u002Farticles\u002Fculture\u002Fj-league","Jリーグの歴史と地域密着 — 1993年開幕から30年",{"articleId":359,"path":360,"title":361},"culture-jinja-tera","\u002Farticles\u002Fculture\u002Fjinja-tera","神社と寺の違い、参拝マナー",{"articleId":363,"path":364,"title":365},"exam-jlpt-n1-dokkai","\u002Farticles\u002Fexams\u002Fjlpt-n1-dokkai","JLPT N1 — 読解問題のアプローチ",{"articleId":367,"path":368,"title":369},"exam-jlpt-n2-business","\u002Farticles\u002Fexams\u002Fjlpt-n2-business","JLPT N2 — ビジネス語彙集中対策",{"articleId":371,"path":372,"title":373},"bj-kaigi-manner","\u002Farticles\u002Fbusiness-japanese\u002Fkaigi-manner","会議のマナーと進め方 — 司会から議事録まで",{"articleId":375,"path":376,"title":377},"living-kakutei-shinkoku","\u002Farticles\u002Fliving-in-japan\u002Fkakutei-shinkoku","確定申告の基本 — 給与所得・副業・控除",{"articleId":379,"path":380,"title":381},"bj-keigo-kihon","\u002Farticles\u002Fbusiness-japanese\u002Fkeigo-kihon","ビジネス敬語の基本 — 尊敬語・謙譲語・丁寧語の使い分け",{"articleId":383,"path":384,"title":385},"law-keihin-hyouji","\u002Farticles\u002Flaw\u002Fkeihin-hyouji","改正景品表示法とステマ規制 — マーケティングの法的注意点",{"articleId":387,"path":388,"title":389},"living-kenkou-hoken","\u002Farticles\u002Fliving-in-japan\u002Fkenkou-hoken","健康保険の入門 — 国保と社保の違い",{"articleId":391,"path":392,"title":393},"living-kosei-nenkin","\u002Farticles\u002Fliving-in-japan\u002Fkosei-nenkin","厚生年金と国民年金 — 老後の備えと現役の負担",{"articleId":395,"path":396,"title":397},"tech-line-llmops","\u002Farticles\u002Ftech\u002Fline-llmops","LINEのLLMOps — 大規模言語モデル運用の取り組み",{"articleId":399,"path":400,"title":401},"tech-line-streaming","\u002Farticles\u002Ftech\u002Fline-streaming","LINEの大規模リアルタイム配信基盤",{"articleId":403,"path":404,"title":405},"living-chintai-keiyaku","\u002Farticles\u002Fliving-in-japan\u002Fliving-chintai-keiyaku","賃貸契約と保証会社 — 礼金・敷金から保証料まで",{"articleId":407,"path":408,"title":409},"living-eijuken","\u002Farticles\u002Fliving-in-japan\u002Fliving-eijuken","永住権申請の最新基準 — 一般・高度専門職ルート比較",{"articleId":411,"path":412,"title":413},"living-engineer-visa","\u002Farticles\u002Fliving-in-japan\u002Fliving-engineer-visa","エンジニアの在留資格 — 「技術・人文知識・国際業務」ビザの取得手順",{"articleId":415,"path":416,"title":417},"living-ginkou-koza","\u002Farticles\u002Fliving-in-japan\u002Fliving-ginkou-koza","銀行口座開設とクレジットカード — 外国人エンジニアの実務",{"articleId":419,"path":420,"title":421},"living-hikkoshi-checklist","\u002Farticles\u002Fliving-in-japan\u002Fliving-hikkoshi-checklist","引越し手続きチェックリスト — 役所・ライフライン・住所変更",{"articleId":423,"path":424,"title":425},"living-koudo-senmon","\u002Farticles\u002Fliving-in-japan\u002Fliving-koudo-senmon","高度専門職ビザの実務 — ポイント制度と特権",{"articleId":427,"path":428,"title":429},"culture-matsuri","\u002Farticles\u002Fculture\u002Fmatsuri","日本の祭り — 季節と地域の象徴",{"articleId":431,"path":432,"title":433},"bj-meishi-koukan","\u002Farticles\u002Fbusiness-japanese\u002Fmeishi-koukan","名刺交換の作法 — 第一印象を決める数十秒",{"articleId":435,"path":436,"title":437},"tech-mercari-merpay-id","\u002Farticles\u002Ftech\u002Fmercari-merpay-id","メルペイのID基盤 — eKYC・本人確認の技術",{"articleId":439,"path":440,"title":441},"tech-mercari-microservices","\u002Farticles\u002Ftech\u002Fmercari-microservices-migration","Mercariのマイクロサービス移行 — モノリスから次世代へ",{"articleId":88,"path":443,"title":444},"\u002Farticles\u002Ftech\u002Fmoneyforward-multitenant-saas","Money Forwardのマルチテナント設計 — データ分離とセキュリティ",{"articleId":446,"path":447,"title":448},"bj-nemawashi-ringi","\u002Farticles\u002Fbusiness-japanese\u002Fnemawashi-ringi","根回しと稟議 — 日本企業の意思決定の仕組み",{"articleId":450,"path":451,"title":452},"living-nenmatsu-chousei","\u002Farticles\u002Fliving-in-japan\u002Fnenmatsu-chousei","年末調整の仕組み — 会社員のための税精算",{"articleId":454,"path":455,"title":456},"bj-1on1","\u002Farticles\u002Fbusiness-japanese\u002Fone-on-one","1on1ミーティングの活用法 — 上司と部下の対話",{"articleId":458,"path":459,"title":460},"bj-online-kaigi","\u002Farticles\u002Fbusiness-japanese\u002Fonline-kaigi","オンライン会議のエチケット — Zoom時代のビジネスマナー",{"articleId":462,"path":463,"title":464},"culture-onsen","\u002Farticles\u002Fculture\u002Fonsen","温泉文化と入浴マナー — 名湯巡りの楽しみ方",{"articleId":466,"path":467,"title":468},"culture-pro-baseball","\u002Farticles\u002Fculture\u002Fpro-baseball","プロ野球と高校野球 — 国民的スポーツの二つの顔",{"articleId":470,"path":471,"title":472},"culture-ramen","\u002Farticles\u002Fculture\u002Framen","ラーメン地域ごとの違い — 札幌・博多・喜多方",{"articleId":474,"path":475,"title":476},"tech-recruit-data-platform","\u002Farticles\u002Ftech\u002Frecruit-data-platform","Recruit データ基盤刷新事例 — 数十サービスの統合",{"articleId":478,"path":479,"title":480},"law-roukikihou-kihon","\u002Farticles\u002Flaw\u002Froukikihou-kihon","労働基準法の基本 — 労働時間・休憩・残業規制",{"articleId":482,"path":483,"title":484},"culture-sado","\u002Farticles\u002Fculture\u002Fsado","茶道入門 — 千利休と侘び寂びの精神",{"articleId":486,"path":487,"title":488},"culture-sandou","\u002Farticles\u002Fculture\u002Fsandou","茶華書三道 — 日本の精神を体現する三つの道",{"articleId":490,"path":491,"title":492},"culture-seasonal-events","\u002Farticles\u002Fculture\u002Fseasonal-events","季節の行事 — 正月から年末まで日本の年中行事",{"articleId":494,"path":495,"title":496},"exam-sg","\u002Farticles\u002Fexams\u002Fsg","情報セキュリティマネジメント試験 — 管理者向けセキュリティ",{"articleId":498,"path":499,"title":500},"bj-shagai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshagai-mail","社外メールの書き方 — お詫び・依頼・確認",{"articleId":502,"path":503,"title":504},"bj-shanai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshanai-mail","社内メールの書き方 — 件名から結びまで",{"articleId":506,"path":507,"title":508},"culture-sumo","\u002Farticles\u002Fculture\u002Fsumo","大相撲 — 番付と力士の生活",{"articleId":510,"path":511,"title":512},"culture-sushi","\u002Farticles\u002Fculture\u002Fsushi","寿司の歴史と種類 — なれずしから江戸前まで",{"articleId":514,"path":515,"title":516},"culture-washoku","\u002Farticles\u002Fculture\u002Fwashoku","和食 — ユネスコ無形文化遺産と一汁三菜",{"articleId":518,"path":519,"title":520},"law-yuukyuu-kyuuka","\u002Farticles\u002Flaw\u002Fyuukyuu-kyuuka","有給休暇の取得ルールと最新改正",{"articleId":522,"path":523,"title":524},"kjh-k1-h04-anzen-kanri","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fanzen-kanri","課題Ⅰ 第４編① 個人データに関する義務 ― 正確性の確保・安全管理措置・漏えい報告",{"articleId":526,"path":527,"title":528},"bill-one-auth","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fbill-one-auth","インボイス管理サービスBill Oneの認証を内製認証基盤に置き換えて認証基盤のコストを削減した話",{"articleId":530,"path":531,"title":532},"contract-one-vision","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fcontract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造",{"articleId":534,"path":535,"title":536},"kjh-k1-h04-daisan-sha-teikyou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fdaisan-sha-teikyou","課題Ⅰ 第４編② 第三者提供の制限 ― 同意・オプトアウト・非該当類型",{"articleId":538,"path":539,"title":540},"eight-web-renewal","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Feight-web-renewal","Web版Eightのリニューアルと、安全なリリースのための取り組み",{"articleId":542,"path":543,"title":544},"kjh-k1-h04-gaikoku-kiroku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fgaikoku-kiroku","課題Ⅰ 第４編③ 外国にある第三者への提供の制限・記録義務・確認義務（法28条〜30条）",{"articleId":546,"path":547,"title":548},"kjh-k2-h04-gijutsu-jisshi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-jisshi","課題Ⅱ 第４編② 技術的安全管理措置の実施項目",{"articleId":550,"path":551,"title":552},"kjh-k2-h04-gijutsu-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-kiso","課題Ⅱ 第４編① 技術的セキュリティ対策の基礎知識",{"articleId":554,"path":555,"title":556},"kjh-k1-h01-hotaikei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhotaikei","課題Ⅰ 第１編 個人情報保護の法体系と各種認定制度",{"articleId":558,"path":559,"title":560},"kjh-k1-h06-hoyu-data","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhoyu-data","課題Ⅰ 第６編 保有個人データに関する義務",{"articleId":562,"path":563,"title":564},"kjh-k1-h07-kamei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkamei-kakou","課題Ⅰ 第７編 仮名加工情報（法41条・42条）",{"articleId":566,"path":567,"title":568},"kjh-k1-h05-kanren-joho","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkanren-joho","課題Ⅰ 第５編 個人関連情報に関する義務（法31条）",{"articleId":570,"path":571,"title":572},"kjh-k1-h02-kihon-rinen","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkihon-rinen","課題Ⅰ 第２編 個人情報保護法の目的・基本理念と用語の定義",{"articleId":574,"path":575,"title":576},"kjh-k1-h09-jikkousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h09-jikkousei","課題Ⅰ 第９編 実効性を担保する仕組み等",{"articleId":578,"path":579,"title":580},"kjh-k1-h10-gyousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h10-gyousei","課題Ⅰ 第10編 行政機関等における個人情報等の取扱い",{"articleId":582,"path":583,"title":584},"kjh-k1-h11-my-number-hogo","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-hogo","課題Ⅰ 第11編② マイナンバー法 ― 特定個人情報の提供制限・保護・監督・罰則（法19条〜57条）",{"articleId":586,"path":587,"title":588},"kjh-k1-h11-my-number-sousoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-sousoku","課題Ⅰ 第11編① マイナンバー法 ― 総則・個人番号・個人番号カード（法1条〜18条の5）",{"articleId":590,"path":591,"title":592},"kjh-k2-h01-guideline","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-guideline","課題Ⅱ 第１編② セキュリティ対策基準とガイドライン",{"articleId":594,"path":595,"title":596},"kjh-k2-h01-security-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-security-kiso","課題Ⅱ 第１編① 情報セキュリティの基礎と脅威",{"articleId":598,"path":599,"title":600},"kjh-k2-h02-anzen-kanri-sochi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-anzen-kanri-sochi","課題Ⅱ 第２編② 組織的・人的セキュリティ ― 安全管理措置・委託先監督・事故対応",{"articleId":602,"path":603,"title":604},"kjh-k2-h02-soshiki-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-soshiki-kiso","課題Ⅱ 第２編① 組織的・人的セキュリティ ― 基本方針の策定からリスク管理・規程整備まで",{"articleId":606,"path":607,"title":608},"kjh-k2-h03-office","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Foffice","課題Ⅱ 第３編 オフィスセキュリティ",{"articleId":610,"path":611,"title":612},"kjh-k1-h03-riyou-mokuteki","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Friyou-mokuteki","課題Ⅰ 第３編① 利用目的の特定・変更と利用目的による制限、不適正な利用の禁止",{"articleId":614,"path":615,"title":616},"sansan-data-intelligence","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-data-intelligence","Sansan Data Intelligenceリリースに寄せて",{"articleId":618,"path":619,"title":620},"sansan-engineer-team-infra","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-engineer-team-infra","Sansan Engineer Team：インフラ戦略部",{"articleId":622,"path":623,"title":624},"sansan-honne-15","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］",{"articleId":626,"path":627,"title":628},"sansan-interview-110","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-110","SIer出身者が活躍する理由とは。Sansanを牽引するプロダクト開発に挑み続ける",{"articleId":630,"path":631,"title":632},"sansan-interview-126","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-126","AIと協働する開発組織、そして技術の深化。Sansan 新CTO笹川が語るビジョン",{"articleId":634,"path":635,"title":636},"sansan-interview-127","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-127","Sansanの技術基盤を関西から築く。新設組織で未来を創る、エンジニアの挑戦",{"articleId":638,"path":639,"title":640},"sansan-interview-130","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦",{"articleId":642,"path":643,"title":644},"sansan-interview-40","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。",{"articleId":646,"path":647,"title":648},"sansan-oyaco","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-oyaco","仕事と子育ての両立を支援する制度「OYACO」",{"articleId":650,"path":651,"title":652},"kjh-k1-h03-tekisei-shutoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftekisei-shutoku","課題Ⅰ 第３編② 適正な取得・要配慮個人情報・利用目的の通知",{"articleId":654,"path":655,"title":656},"kjh-k1-h08-tokumei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftokumei-kakou","課題Ⅰ 第８編 匿名加工情報に関する義務等（法43条〜46条）"]