[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"quiz:tech-cybozu-kintone-no-code-quiz":3,"quiz-article-index":160},{"quizId":4,"title":5,"titleEn":6,"topicPath":7,"questions":8},"tech-cybozu-kintone-no-code-quiz","テック確認テスト — kintoneのローコード戦略","Tech Quiz — Kintone's Low-Code Strategy","tech",[9,39,64,88,113,137],{"id":10,"articleId":11,"question":12,"options":15,"correctLabel":17,"explanation":32,"tags":35},"tech-cybozu-kintone-no-code-quiz-q01","tech-cybozu-kintone-no-code",{"en":13,"jp":14},"Which best describes the difference between low-code and no-code?","[ローコード]{ろーこーど:low-code}と[ノーコード]{のーこーど:no-code}の[違い]{ちがい:difference}として[最も]{もっとも:most}[適切]{てきせつ:appropriate}な[説明]{せつめい:description}はどれか？",[16,20,24,28],{"label":17,"jp":18,"en":19},"ア","[ノーコード]{のーこーど:no-code}は[コード]{こーど:code}を[一切]{いっさい:at all}[書か]{かか:writing}ず、[ローコード]{ろーこーど:low-code}は[標準]{ひょうじゅん:standard}[機能]{きのう:features}で[足り]{たり:sufficient}ない[部分]{ぶぶん:parts}を[コード]{こーど:code}で[拡張]{かくちょう:extend}できる。","No-code writes no code at all, while low-code lets you extend with code where standard features are insufficient.",{"label":21,"jp":22,"en":23},"イ","[ローコード]{ろーこーど:low-code}は[専門]{せんもん:specialist}[開発者]{かいはつしゃ:developer}[専用]{せんよう:exclusive}で[非]{ひ:non-}[エンジニア]{えんじにあ:engineer}は[使え]{つかえ:can use}ない。","Low-code is exclusively for specialist developers and cannot be used by non-engineers.",{"label":25,"jp":26,"en":27},"ウ","[ノーコード]{のーこーど:no-code}は[必ず]{かならず:always}オンプレミスで[動作]{どうさ:operates}し、[ローコード]{ろーこーど:low-code}はクラウド[専用]{せんよう:exclusive}である。","No-code always runs on-premises, and low-code is cloud-only.",{"label":29,"jp":30,"en":31},"エ","[両者]{りょうしゃ:the two}は[完全]{かんぜん:completely}に[同じ]{おなじ:same}[意味]{いみ:meaning}で、[呼び方]{よびかた:naming}が[違う]{ちがう:differs}だけである。","The two have completely identical meanings and only differ in naming.",{"en":33,"jp":34},"No-code is completed without writing code, whereas low-code is a mechanism that supplements with code where standard features fall short. kintone falls into the latter — front-line teams use it as no-code, while developers extend it with JavaScript. (B), (C), and (D) are all wrong.","[ノーコード]{のーこーど:no-code}は[コード]{こーど:code}を[書か]{かか:write}ずに[完結]{かんけつ:completed}するのに[対し]{たいし:whereas}、[ローコード]{ろーこーど:low-code}は[標準]{ひょうじゅん:standard}[機能]{きのう:features}で[足り]{たり:sufficient}ない[部分]{ぶぶん:parts}を[コード]{こーど:code}で[補える]{おぎなえる:supplement}[仕組み]{しくみ:mechanism}です。kintoneは[後者]{こうしゃ:the latter}に[属し]{ぞくし:to belong}、[現場]{げんば:front-line}は[ノーコード]{のーこーど:no-code}で[使い]{つかい:use}、[開発者]{かいはつしゃ:developer}は[JavaScript]{じゃばすくりぷと:JavaScript}で[拡張]{かくちょう:extend}できます。イ・ウ・エは[いずれ]{いずれ:any}も[誤り]{あやまり:wrong}です。",[36,37,38],"low-code","no-code","definition",{"id":40,"articleId":11,"question":41,"options":44,"correctLabel":17,"explanation":57,"tags":60},"tech-cybozu-kintone-no-code-quiz-q02",{"en":42,"jp":43},"Which most accurately describes kintone's extension means (customize \u002F plugin)?","kintoneが[提供]{ていきょう:provides}する[拡張]{かくちょう:extension}[手段]{しゅだん:means}（[カスタマイズ]{かすたまいず:customize}・[プラグイン]{ぷらぐいん:plugin}）の[説明]{せつめい:description}として[最も]{もっとも:most}[正確]{せいかく:accurate}なものはどれか？",[45,48,51,54],{"label":17,"jp":46,"en":47},"[カスタマイズ]{かすたまいず:customize}は[個別]{こべつ:individual}アプリに[書き込む]{かきこむ:written into}JavaScript\u002FCSS、[プラグイン]{ぷらぐいん:plugin}は[再利用]{さいりよう:reusable}[可能]{かのう:possible}な[機能]{きのう:feature}パッケージである。","Customize is JavaScript\u002FCSS written into individual apps; plugins are reusable feature packages.",{"label":21,"jp":49,"en":50},"[両者]{りょうしゃ:both}とも[サイボウズ]{さいぼうず:Cybozu}[公式]{こうしき:official}が[作る]{つくる:builds}もので、[第三者]{だいさんしゃ:third party}は[一切]{いっさい:at all}[開発]{かいはつ:develop}できない。","Both are built by official Cybozu only; third parties cannot develop them at all.",{"label":25,"jp":52,"en":53},"[カスタマイズ]{かすたまいず:customize}は[Python]{ぱいそん:Python}、[プラグイン]{ぷらぐいん:plugin}は[Ruby]{るびー:Ruby}で[書く]{かく:write}[必要]{ひつよう:required}がある。","Customize must be written in Python, and plugins in Ruby.",{"label":29,"jp":55,"en":56},"[カスタマイズ]{かすたまいず:customize}と[プラグイン]{ぷらぐいん:plugin}は[同一]{どういつ:identical}の[機能]{きのう:feature}で、[呼び方]{よびかた:naming}が[違う]{ちがう:differs}だけである。","Customize and plugin are identical features, only differing in naming.",{"en":58,"jp":59},"kintone provides two layers of extension: customize is JavaScript\u002FCSS written per app, while plugins are reusable packages that can be distributed. Plugins are also distributed by partner companies through the official marketplace, so (B) is wrong. (C) and (D) are also wrong.","kintoneは[二]{ふた:two}[層]{そう:layer}の[拡張]{かくちょう:extension}[手段]{しゅだん:means}を[用意]{ようい:provides}しています。[カスタマイズ]{かすたまいず:customize}は[アプリ]{あぷり:app}ごとに[書き込む]{かきこむ:written}JavaScript\u002FCSS、[プラグイン]{ぷらぐいん:plugin}は[再利用]{さいりよう:reusable}[可能]{かのう:possible}に[配布]{はいふ:distribute}できる[パッケージ]{ぱっけーじ:package}です。[プラグイン]{ぷらぐいん:plugin}は[公式]{こうしき:official}[マーケットプレイス]{まーけっとぷれいす:marketplace}で[パートナー]{ぱーとなー:partner}[企業]{きぎょう:companies}も[配布]{はいふ:distribute}するため、イも[誤り]{あやまり:wrong}です。ウとエも[誤り]{あやまり:wrong}。",[61,62,63],"customize","plugin","extension-layers",{"id":65,"articleId":11,"question":66,"options":69,"correctLabel":17,"explanation":82,"tags":85},"tech-cybozu-kintone-no-code-quiz-q03",{"en":67,"jp":68},"Which most accurately describes the concept of 'citizen developer'?","「[市民]{しみん:citizen}[開発者]{かいはつしゃ:developer}」という[概念]{がいねん:concept}を[最も]{もっとも:most}[正確]{せいかく:accurately}に[説明]{せつめい:describes}しているのはどれか？",[70,73,76,79],{"label":17,"jp":71,"en":72},"[専門]{せんもん:specialist}の[ソフトウェア]{そふとうぇあ:software}[開発者]{かいはつしゃ:developer}ではなく、[業務]{ぎょうむ:business}[現場]{げんば:front-line}の[人]{ひと:person}が[自ら]{みずから:by themselves}[業務]{ぎょうむ:business}アプリを[作る]{つくる:builds}[人]{ひと:person}のこと。","A person on the business front line — not a specialist software developer — who builds business apps themselves.",{"label":21,"jp":74,"en":75},"[行政]{ぎょうせい:government}[機関]{きかん:institution}に[所属]{しょぞく:belongs}する[公務員]{こうむいん:civil servant}の[開発者]{かいはつしゃ:developer}のこと。","A developer who is a civil servant belonging to a government institution.",{"label":25,"jp":77,"en":78},"[認定]{にんてい:certified}[資格]{しかく:qualification}を[持つ]{もつ:holds}[サイボウズ]{さいぼうず:Cybozu}[公式]{こうしき:official}の[開発]{かいはつ:development}[パートナー]{ぱーとなー:partner}のこと。","An official Cybozu development partner who holds a certified qualification.",{"label":29,"jp":80,"en":81},"[フリーランス]{ふりーらんす:freelance}で[働く]{はたらく:works}[シニア]{しにあ:senior}[エンジニア]{えんじにあ:engineer}のこと。","A senior engineer working as a freelancer.",{"en":83,"jp":84},"A citizen developer refers to the movement where people on the business front line — not specialist developers — build apps themselves with low-code\u002Fno-code tools. The culture of HR or sales staff building business apps themselves links to the in-house-development drive trend. (B), (C), and (D) all differ from the common definition.","[市民]{しみん:citizen}[開発者]{かいはつしゃ:developer}（citizen developer）は、[専門]{せんもん:specialist}の[開発者]{かいはつしゃ:developer}ではない[業務]{ぎょうむ:business}[現場]{げんば:front-line}の[人]{ひと:people}が[ローコード]{ろーこーど:low-code}\u002F[ノーコード]{のーこーど:no-code}[ツール]{つーる:tools}で[自ら]{みずから:themselves}アプリを[作る]{つくる:building}[動き]{うごき:movement}を[指し]{さし:refers to}ます。[人事]{じんじ:HR}や[営業]{えいぎょう:sales}[事務]{じむ:office}の[担当者]{たんとうしゃ:staff}が[自分]{じぶん:themselves}で[業務]{ぎょうむ:business}アプリを[作る]{つくる:build}[文化]{ぶんか:culture}は、[内製化]{ないせいか:in-house development}[推進]{すいしん:drive}[トレンド]{とれんど:trend}と[結びついて]{むすびついて:linked}います。イ・ウ・エは[いずれ]{いずれ:any}も[一般的]{いっぱんてき:common}な[定義]{ていぎ:definition}とは[異なり]{ことなり:differs}ます。",[86,87],"citizen-developer","in-house-development",{"id":89,"articleId":11,"question":90,"options":93,"correctLabel":17,"explanation":106,"tags":109},"tech-cybozu-kintone-no-code-quiz-q04",{"en":91,"jp":92},"What best describes the comparison between kintone and Salesforce \u002F Notion DB?","kintoneと[Salesforce]{せーるすふぉーす:Salesforce}・[Notion]{のーしょん:Notion}データベースの[比較]{ひかく:comparison}として[最も]{もっとも:most}[適切]{てきせつ:appropriate}な[説明]{せつめい:description}はどれか？",[94,97,100,103],{"label":17,"jp":95,"en":96},"[Salesforce]{せーるすふぉーす:Salesforce}はCRM[中心]{ちゅうしん:center}の[強力]{きょうりょく:powerful}な[企業]{きぎょう:enterprise}[向け]{むけ:platform}で[専門]{せんもん:specialist}[人材]{じんざい:talent}が[必要]{ひつよう:required}、[Notion]{のーしょん:Notion} DBは[小]{しょう:small}[規模]{きぼ:scale}[チーム]{ちーむ:team}[向け]{むけ:for}の[軽量]{けいりょう:lightweight}[テーブル]{てーぶる:table}、kintoneはその[中間]{ちゅうかん:middle}で[現場]{げんば:front-line}が[業務]{ぎょうむ:business}を[回す]{まわす:operate}[領域]{りょういき:domain}に[特化]{とっか:specialized}している。","Salesforce is a powerful CRM-centered enterprise platform requiring specialist talent, Notion DB is a lightweight table for small teams, and kintone sits between them, specialized for the domain of front-line teams running their own operations.",{"label":21,"jp":98,"en":99},"[三]{さん:three}[製品]{せいひん:products}とも[完全]{かんぜん:fully}[同一]{どういつ:identical}の[機能]{きのう:feature}・[ターゲット]{たーげっと:target}で、[価格]{かかく:price}だけが[違う]{ちがう:differs}。","All three products have entirely identical features and targets, with only price differing.",{"label":25,"jp":101,"en":102},"kintoneは[Salesforce]{せーるすふぉーす:Salesforce}の[公式]{こうしき:official}[サブセット]{さぶせっと:subset}として[サイボウズ]{さいぼうず:Cybozu}が[再]{さい:re-}[配布]{はいふ:distributing}している[製品]{せいひん:product}である。","kintone is a product Cybozu redistributes as an official subset of Salesforce.",{"label":29,"jp":104,"en":105},"[Notion]{のーしょん:Notion}データベースは[B2B]{びーつーびー:B2B}[専用]{せんよう:dedicated}でREST APIを[持た]{もた:have}ない。","Notion DB is B2B-only and has no REST API.",{"en":107,"jp":108},"kintone is positioned between Salesforce (CRM-centered, enterprise scale) and Notion DB (document-integrated, small scale), specialized for the domain of 'front-line teams building and running their own operations.' (B), (C), and (D) all differ from the facts.","kintoneは[Salesforce]{せーるすふぉーす:Salesforce}（CRM[中心]{ちゅうしん:center}・[企業]{きぎょう:enterprise}[規模]{きぼ:scale}）と[Notion]{のーしょん:Notion}データベース（[ドキュメント]{どきゅめんと:document}[一体型]{いったいがた:integrated}・[小]{しょう:small}[規模]{きぼ:scale}）の[中間]{ちゅうかん:middle}に[位置]{いち:positioned}し、「[現場]{げんば:front-line}が[作って]{つくって:build}[業務]{ぎょうむ:business}を[回す]{まわす:operate}」[領域]{りょういき:domain}に[特化]{とっか:specialized}しています。イ・ウ・エは[いずれ]{いずれ:any}も[事実]{じじつ:fact}と[異なり]{ことなり:differs}ます。",[110,111,112],"competition","salesforce","notion",{"id":114,"articleId":11,"question":115,"options":118,"correctLabel":17,"explanation":131,"tags":134},"tech-cybozu-kintone-no-code-quiz-q05",{"en":116,"jp":117},"Which most accurately describes kintone's REST API?","kintoneのREST APIに[関する]{かんする:about}[記述]{きじゅつ:description}として[最も]{もっとも:most}[正確]{せいかく:accurate}なものはどれか？",[119,122,125,128],{"label":17,"jp":120,"en":121},"[全]{ぜん:all}アプリに[対して]{たいして:for}REST APIが[自動]{じどう:automatically}[公開]{こうかい:exposed}され、[フィールド]{ふぃーるど:field}[追加]{ついか:added}と[同時]{どうじ:same time}に[対応]{たいおう:corresponding}するエンドポイントが[生成]{せいせい:generated}される。","A REST API is automatically exposed for every app, and corresponding endpoints are generated the moment a field is added.",{"label":21,"jp":123,"en":124},"[有料]{ゆうりょう:paid}の[追加]{ついか:additional}[契約]{けいやく:contract}を[結ば]{むすば:concluded}ない[限り]{かぎり:unless}APIは[一切]{いっさい:at all}[利用]{りよう:used}できない。","Unless an additional paid contract is concluded, the API cannot be used at all.",{"label":25,"jp":126,"en":127},"API は[読み込み]{よみこみ:read}[専用]{せんよう:only}で、データの[作成]{さくせい:creation}・[更新]{こうしん:update}・[削除]{さくじょ:deletion}は[できない]{できない:cannot do}。","The API is read-only and cannot create, update, or delete data.",{"label":29,"jp":129,"en":130},"REST APIは[サイボウズ]{さいぼうず:Cybozu}[社内]{しゃない:internal}[専用]{せんよう:only}で、[顧客]{こきゃく:customer}には[公開]{こうかい:disclosed}されていない。","The REST API is for internal Cybozu use only and is not disclosed to customers.",{"en":132,"jp":133},"kintone is designed to automatically expose a REST API for every app, with endpoints generated the instant a field is added. This enables immediate data integration with other systems and visualization in BI tools — a critical element preventing low-code products from becoming isolated silos. (B), (C), and (D) are all wrong.","kintoneは[全]{ぜん:all}アプリに[対し]{たいし:for}REST APIを[自動]{じどう:automatically}[公開]{こうかい:exposes}し、[フィールド]{ふぃーるど:field}を[追加]{ついか:add}した[瞬間]{しゅんかん:instant}にエンドポイントが[生成]{せいせい:generated}される[設計]{せっけい:design}です。これにより[他]{ほか:other}システムとのデータ[連携]{れんけい:integration}や[BI]{びーあい:BI}[ツール]{つーる:tools}での[可視化]{かしか:visualization}が[即座]{そくざ:immediately}に[実現]{じつげん:achievable}でき、[ローコード]{ろーこーど:low-code}[製品]{せいひん:products}が[孤立]{こりつ:isolated}した[サイロ]{さいろ:silo}にならないための[重要]{じゅうよう:critical}な[要素]{ようそ:element}です。イ・ウ・エは[いずれ]{いずれ:any}も[誤り]{あやまり:wrong}です。",[135,136],"rest-api","integration",{"id":138,"articleId":11,"question":139,"options":142,"correctLabel":17,"explanation":155,"tags":158},"tech-cybozu-kintone-no-code-quiz-q06",{"en":140,"jp":141},"Which best describes the in-house development drive trend?","[内製化]{ないせいか:in-house development}[推進]{すいしん:drive}トレンドに[関する]{かんする:about}[記述]{きじゅつ:description}として[最も]{もっとも:most}[適切]{てきせつ:appropriate}なものはどれか？",[143,146,149,152],{"label":17,"jp":144,"en":145},"[ビジネス]{びじねす:business}[変化]{へんか:change}の[速さ]{はやさ:speed}に[追いつく]{おいつく:keep up}ため、[従来]{じゅうらい:conventional}の[外部]{がいぶ:external}[ベンダー]{べんだー:vendor}[委託]{いたく:outsourcing}から、[現場]{げんば:front-line}[自身]{じしん:itself}が[システム]{しすてむ:system}を[作り]{つくり:build}[変える]{かえる:change}[体制]{たいせい:structure}への[転換]{てんかん:shift}を[指す]{さす:refers}。","It refers to the shift from conventional outsourcing to external vendors toward a structure where front-line teams themselves build and change systems, in order to keep up with the speed of business change.",{"label":21,"jp":147,"en":148},"[全て]{すべて:all}の[システム]{しすてむ:system}[開発]{かいはつ:development}を[海外]{かいがい:overseas}の[開発]{かいはつ:development}[拠点]{きょてん:hubs}に[移管]{いかん:transfer}する[流れ]{ながれ:trend}のことである。","It refers to the trend of transferring all system development to overseas development hubs.",{"label":25,"jp":150,"en":151},"[国産]{こくさん:domestic}クラウド[製品]{せいひん:product}の[利用]{りよう:use}を[政府]{せいふ:government}が[義務]{ぎむ:mandates}づける[政策]{せいさく:policy}を[指す]{さす:refers}。","It refers to a policy where the government mandates the use of domestic cloud products.",{"label":29,"jp":153,"en":154},"[業務]{ぎょうむ:business}[アプリ]{あぷり:app}を[全て]{すべて:all}[紙]{かみ:paper}と[Excel]{えくせる:Excel}に[戻す]{もどす:revert}[運動]{うんどう:movement}のことである。","It refers to a movement to revert all business apps back to paper and Excel.",{"en":156,"jp":157},"In-house development drive is the trend of shifting from conventionally outsourcing system development to external vendors, to a structure where front-line teams themselves build and change systems, in order to keep up with the speed of business change. Low-code products like kintone grew on this tailwind. (B), (C), and (D) are all wrong.","[内製化]{ないせいか:in-house development}[推進]{すいしん:drive}は、[従来]{じゅうらい:conventionally}[外部]{がいぶ:external}[ベンダー]{べんだー:vendors}に[委託]{いたく:outsourced}していた[システム]{しすてむ:system}[開発]{かいはつ:development}を、[ビジネス]{びじねす:business}[変化]{へんか:change}の[速さ]{はやさ:speed}に[追いつく]{おいつく:keep up}ため[現場]{げんば:front-line}[自身]{じしん:itself}が[作り]{つくり:build}[変える]{かえる:change}[体制]{たいせい:structure}に[転換]{てんかん:shift}する[流れ]{ながれ:trend}です。kintoneのような[ローコード]{ろーこーど:low-code}[製品]{せいひん:product}はこの[流れ]{ながれ:trend}を[追い風]{おいかぜ:tailwind}に[成長]{せいちょう:grew}しました。イ・ウ・エは[いずれ]{いずれ:any}も[誤り]{あやまり:wrong}です。",[87,159],"trend",{"culture-anime-studio-ghibli":161,"culture-bonsai-art":165,"tech-cybozu-kintone-no-code":169,"living-denki-gas-suidou":172,"tech-gree-mobile-game-ops":176,"culture-green-tea-types":180,"living-gym-fitness":184,"living-internet-hikari":188,"living-jisha-de-kau":192,"exam-jlpt-n3-grammar":196,"exam-jlpt-n3-vocab":200,"bj-job-gata-koyou":204,"culture-kabuki-noh-bunraku":208,"bj-karoushi-hatarakikata":212,"living-keitai-mobile-plan":216,"living-konbini-atm-banking":220,"living-kosodate-hoiku":224,"culture-nihon-teien":228,"bj-nomikai-survival":232,"tech-pixiv-image-cdn":236,"culture-sake-shochu":240,"bj-sankyu-ikukyu":244,"tech-sansan-eight-platform":248,"culture-shichi-go-san":252,"bj-shukatsu-shinsotsu":256,"tech-smartnews-recommendation":260,"bj-taishoku-todoke":264,"bj-telework-policy":268,"bj-tenshoku-resume":272,"tech-yahoo-japan-search":276,"culture-anime-business":280,"exam-ap":284,"exam-aws-japan":288,"law-chosakuken":292,"tech-cookpad-recipe-search":296,"tech-cybozu-kintone-api":300,"tech-dena-observability":304,"law-denshi-chouho":308,"tech-digital-cho-cloud":312,"exam-fe":316,"tech-freee-accounting":320,"law-furiransu-hou":324,"law-harassment":328,"tech-hatena-mackerel":332,"bj-hourensou":336,"bj-hyouka-mendan":340,"law-invoice":344,"exam-it-passport":348,"culture-izakaya":352,"culture-j-league":356,"culture-jinja-tera":360,"exam-jlpt-n1-dokkai":364,"exam-jlpt-n2-business":368,"bj-kaigi-manner":372,"living-kakutei-shinkoku":376,"bj-keigo-kihon":380,"law-keihin-hyouji":384,"living-kenkou-hoken":388,"living-kosei-nenkin":392,"tech-line-llmops":396,"tech-line-streaming":400,"living-chintai-keiyaku":404,"living-eijuken":408,"living-engineer-visa":412,"living-ginkou-koza":416,"living-hikkoshi-checklist":420,"living-koudo-senmon":424,"culture-matsuri":428,"bj-meishi-koukan":432,"tech-mercari-merpay-id":436,"tech-mercari-microservices":440,"tech-mf-multitenant":444,"bj-nemawashi-ringi":448,"living-nenmatsu-chousei":452,"bj-1on1":456,"bj-online-kaigi":460,"culture-onsen":464,"culture-pro-baseball":468,"culture-ramen":472,"tech-recruit-data-platform":476,"law-roukikihou-kihon":480,"culture-sado":484,"culture-sandou":488,"culture-seasonal-events":492,"exam-sg":496,"bj-shagai-mail":500,"bj-shanai-mail":504,"culture-sumo":508,"culture-sushi":512,"culture-washoku":516,"law-yuukyuu-kyuuka":520,"kjh-k1-h04-anzen-kanri":524,"bill-one-auth":528,"contract-one-vision":532,"kjh-k1-h04-daisan-sha-teikyou":536,"eight-web-renewal":540,"kjh-k1-h04-gaikoku-kiroku":544,"kjh-k2-h04-gijutsu-jisshi":548,"kjh-k2-h04-gijutsu-kiso":552,"kjh-k1-h01-hotaikei":556,"kjh-k1-h06-hoyu-data":560,"kjh-k1-h07-kamei-kakou":564,"kjh-k1-h05-kanren-joho":568,"kjh-k1-h02-kihon-rinen":572,"kjh-k1-h09-jikkousei":576,"kjh-k1-h10-gyousei":580,"kjh-k1-h11-my-number-hogo":584,"kjh-k1-h11-my-number-sousoku":588,"kjh-k2-h01-guideline":592,"kjh-k2-h01-security-kiso":596,"kjh-k2-h02-anzen-kanri-sochi":600,"kjh-k2-h02-soshiki-kiso":604,"kjh-k2-h03-office":608,"kjh-k1-h03-riyou-mokuteki":612,"sansan-data-intelligence":616,"sansan-engineer-team-infra":620,"sansan-honne-15":624,"sansan-interview-110":628,"sansan-interview-126":632,"sansan-interview-127":636,"sansan-interview-130":640,"sansan-interview-40":644,"sansan-oyaco":648,"kjh-k1-h03-tekisei-shutoku":652,"kjh-k1-h08-tokumei-kakou":656},{"articleId":162,"path":163,"title":164},"culture-anime-studio-ghibli","\u002Farticles\u002Fculture\u002Fanime-studio-ghibli","スタジオジブリ作品史 — 宮崎駿・高畑勲・鈴木敏夫が築いた40年",{"articleId":166,"path":167,"title":168},"culture-bonsai-art","\u002Farticles\u002Fculture\u002Fbonsai-art","盆栽の世界 — 小宇宙を育てる日本の芸術",{"articleId":11,"path":170,"title":171},"\u002Farticles\u002Ftech\u002Fcybozu-kintone-no-code","kintoneのローコード戦略 — 業務アプリを誰でも作れる仕組み",{"articleId":173,"path":174,"title":175},"living-denki-gas-suidou","\u002Farticles\u002Fliving-in-japan\u002Fdenki-gas-suidou","電気・ガス・水道の契約 — 引越し時のライフライン手続き",{"articleId":177,"path":178,"title":179},"tech-gree-mobile-game-ops","\u002Farticles\u002Ftech\u002Fgree-mobile-game-ops","GREEのモバイルゲーム運用 — リアルタイム対戦と決済の裏側",{"articleId":181,"path":182,"title":183},"culture-green-tea-types","\u002Farticles\u002Fculture\u002Fgreen-tea-types","日本茶の種類と淹れ方 — 煎茶・玉露・抹茶の違い",{"articleId":185,"path":186,"title":187},"living-gym-fitness","\u002Farticles\u002Fliving-in-japan\u002Fgym-fitness","ジムとフィットネスクラブ — 入会から解約までの実務ガイド",{"articleId":189,"path":190,"title":191},"living-internet-hikari","\u002Farticles\u002Fliving-in-japan\u002Finternet-hikari-keiyaku","光回線とネット契約 — フレッツ・NURO・auひかり比較",{"articleId":193,"path":194,"title":195},"living-jisha-de-kau","\u002Farticles\u002Fliving-in-japan\u002Fjisha-de-kau","日本で不動産を買う — 外国人でも住宅ローンを組む方法",{"articleId":197,"path":198,"title":199},"exam-jlpt-n3-grammar","\u002Farticles\u002Fexams\u002Fjlpt-n3-grammar","JLPT N3 文法 — 初級から中級への橋渡し",{"articleId":201,"path":202,"title":203},"exam-jlpt-n3-vocab","\u002Farticles\u002Fexams\u002Fjlpt-n3-vocab","JLPT N3 語彙対策 — 1500語をどう攻略するか",{"articleId":205,"path":206,"title":207},"bj-job-gata-koyou","\u002Farticles\u002Fbusiness-japanese\u002Fjob-gata-koyou","ジョブ型雇用への移行 — メンバーシップ型からの脱却",{"articleId":209,"path":210,"title":211},"culture-kabuki-noh-bunraku","\u002Farticles\u002Fculture\u002Fkabuki-noh-bunraku","歌舞伎・能・文楽 — 日本三大伝統演劇の世界",{"articleId":213,"path":214,"title":215},"bj-karoushi-hatarakikata","\u002Farticles\u002Fbusiness-japanese\u002Fkaroushi-hatarakikata","過労死と働き方改革 — 残業規制の歴史と現状",{"articleId":217,"path":218,"title":219},"living-keitai-mobile-plan","\u002Farticles\u002Fliving-in-japan\u002Fkeitai-mobile-plan","携帯電話契約の選び方 — 大手キャリア・MVNO・eSIM完全ガイド",{"articleId":221,"path":222,"title":223},"living-konbini-atm-banking","\u002Farticles\u002Fliving-in-japan\u002Fkonbini-atm-banking","コンビニATMと電子マネー — 現金とキャッシュレスのハイブリッド生活",{"articleId":225,"path":226,"title":227},"living-kosodate-hoiku","\u002Farticles\u002Fliving-in-japan\u002Fkosodate-hoiku","子育て支援と保育園 — 児童手当・保活・無償化制度",{"articleId":229,"path":230,"title":231},"culture-nihon-teien","\u002Farticles\u002Fculture\u002Fnihon-teien","日本庭園の世界 — 池泉・枯山水・露地の様式",{"articleId":233,"path":234,"title":235},"bj-nomikai-survival","\u002Farticles\u002Fbusiness-japanese\u002Fnomikai-survival","飲み会・ノミニケーション完全攻略 — 新人エンジニアのサバイバルガイド",{"articleId":237,"path":238,"title":239},"tech-pixiv-image-cdn","\u002Farticles\u002Ftech\u002Fpixiv-image-cdn","pixivの画像配信基盤 — 数億イラストを世界に届ける技術",{"articleId":241,"path":242,"title":243},"culture-sake-shochu","\u002Farticles\u002Fculture\u002Fsake-shochu","日本酒と焼酎入門 — 製法・産地・飲み方の基礎",{"articleId":245,"path":246,"title":247},"bj-sankyu-ikukyu","\u002Farticles\u002Fbusiness-japanese\u002Fsankyu-ikukyu","産休・育休制度の実務 — 取得スケジュールと給付金",{"articleId":249,"path":250,"title":251},"tech-sansan-eight-platform","\u002Farticles\u002Ftech\u002Fsansan-eight-platform","Eight 名刺SaaSの基盤進化 — モバイルから法人向けプラットフォームへ",{"articleId":253,"path":254,"title":255},"culture-shichi-go-san","\u002Farticles\u002Fculture\u002Fshichi-go-san","七五三 — 子供の成長を祝う伝統行事",{"articleId":257,"path":258,"title":259},"bj-shukatsu-shinsotsu","\u002Farticles\u002Fbusiness-japanese\u002Fshukatsu-shinsotsu","新卒就活の流れ — エントリーシートから内定まで",{"articleId":261,"path":262,"title":263},"tech-smartnews-recommendation","\u002Farticles\u002Ftech\u002Fsmartnews-recommendation","SmartNewsの推薦システム — ニュースを最適化する機械学習",{"articleId":265,"path":266,"title":267},"bj-taishoku-todoke","\u002Farticles\u002Fbusiness-japanese\u002Ftaishoku-todoke","退職届と退職願 — 違いと書き方、円満退職への手順",{"articleId":269,"path":270,"title":271},"bj-telework-policy","\u002Farticles\u002Fbusiness-japanese\u002Ftelework-policy","テレワーク制度の現状 — コロナ後の在宅勤務とハイブリッド",{"articleId":273,"path":274,"title":275},"bj-tenshoku-resume","\u002Farticles\u002Fbusiness-japanese\u002Ftenshoku-resume","転職活動の進め方 — 履歴書と職務経歴書の書き方",{"articleId":277,"path":278,"title":279},"tech-yahoo-japan-search","\u002Farticles\u002Ftech\u002Fyahoo-japan-search","Yahoo! JAPAN検索の基盤 — 日本語特化の大規模検索システム",{"articleId":281,"path":282,"title":283},"culture-anime-business","\u002Farticles\u002Fculture\u002Fanime-business","アニメ・漫画文化と産業構造 — グローバル展開の現状",{"articleId":285,"path":286,"title":287},"exam-ap","\u002Farticles\u002Fexams\u002Fap","応用情報技術者試験 — 重点出題分野",{"articleId":289,"path":290,"title":291},"exam-aws-japan","\u002Farticles\u002Fexams\u002Faws-japan","AWS認定 — 日本語受験のコツ",{"articleId":293,"path":294,"title":295},"law-chosakuken","\u002Farticles\u002Flaw\u002Fchosakuken","著作権法 — エンジニアが知っておくべき基礎",{"articleId":297,"path":298,"title":299},"tech-cookpad-recipe-search","\u002Farticles\u002Ftech\u002Fcookpad-recipe-search-ranking","Cookpadのレシピ検索 — 学習to-rank実装",{"articleId":301,"path":302,"title":303},"tech-cybozu-kintone-api","\u002Farticles\u002Ftech\u002Fcybozu-kintone-api-design","kintone API設計の十年 — 後方互換性との戦い",{"articleId":305,"path":306,"title":307},"tech-dena-observability","\u002Farticles\u002Ftech\u002Fdena-mobile-game-observability","DeNAのモバイルゲーム監視基盤",{"articleId":309,"path":310,"title":311},"law-denshi-chouho","\u002Farticles\u002Flaw\u002Fdenshi-chouho","電子帳簿保存法 — スキャナ保存と電子取引保存の対応",{"articleId":313,"path":314,"title":315},"tech-digital-cho-cloud","\u002Farticles\u002Ftech\u002Fdigital-cho-government-cloud","デジタル庁ガバメントクラウド技術詳細",{"articleId":317,"path":318,"title":319},"exam-fe","\u002Farticles\u002Fexams\u002Ffe","基本情報技術者試験 — シラバス全体像",{"articleId":321,"path":322,"title":323},"tech-freee-accounting","\u002Farticles\u002Ftech\u002Ffreee-accounting-integrity","freeeの会計データ整合性 — 仕訳バランスの自動検証",{"articleId":325,"path":326,"title":327},"law-furiransu-hou","\u002Farticles\u002Flaw\u002Ffuriransu-hou","フリーランス保護法（2024年施行）— 取引適正化のポイント",{"articleId":329,"path":330,"title":331},"law-harassment","\u002Farticles\u002Flaw\u002Fharassment","ハラスメント関連法 — パワハラ・セクハラ・マタハラ防止義務",{"articleId":333,"path":334,"title":335},"tech-hatena-mackerel","\u002Farticles\u002Ftech\u002Fhatena-mackerel-alert-design","MackerelのAlert設計思想",{"articleId":337,"path":338,"title":339},"bj-hourensou","\u002Farticles\u002Fbusiness-japanese\u002Fhourensou","報・連・相 — 日本企業のコミュニケーションの基本",{"articleId":341,"path":342,"title":343},"bj-hyouka-mendan","\u002Farticles\u002Fbusiness-japanese\u002Fhyouka-mendan","評価面談の準備と振り返り",{"articleId":345,"path":346,"title":347},"law-invoice","\u002Farticles\u002Flaw\u002Finvoice-seido","インボイス制度の仕組みと実務 — 適格請求書発行事業者",{"articleId":349,"path":350,"title":351},"exam-it-passport","\u002Farticles\u002Fexams\u002Fit-passport","ITパスポート試験 — 概要と学習法",{"articleId":353,"path":354,"title":355},"culture-izakaya","\u002Farticles\u002Fculture\u002Fizakaya","居酒屋文化と乾杯のマナー — お通しから締めまで",{"articleId":357,"path":358,"title":359},"culture-j-league","\u002Farticles\u002Fculture\u002Fj-league","Jリーグの歴史と地域密着 — 1993年開幕から30年",{"articleId":361,"path":362,"title":363},"culture-jinja-tera","\u002Farticles\u002Fculture\u002Fjinja-tera","神社と寺の違い、参拝マナー",{"articleId":365,"path":366,"title":367},"exam-jlpt-n1-dokkai","\u002Farticles\u002Fexams\u002Fjlpt-n1-dokkai","JLPT N1 — 読解問題のアプローチ",{"articleId":369,"path":370,"title":371},"exam-jlpt-n2-business","\u002Farticles\u002Fexams\u002Fjlpt-n2-business","JLPT N2 — ビジネス語彙集中対策",{"articleId":373,"path":374,"title":375},"bj-kaigi-manner","\u002Farticles\u002Fbusiness-japanese\u002Fkaigi-manner","会議のマナーと進め方 — 司会から議事録まで",{"articleId":377,"path":378,"title":379},"living-kakutei-shinkoku","\u002Farticles\u002Fliving-in-japan\u002Fkakutei-shinkoku","確定申告の基本 — 給与所得・副業・控除",{"articleId":381,"path":382,"title":383},"bj-keigo-kihon","\u002Farticles\u002Fbusiness-japanese\u002Fkeigo-kihon","ビジネス敬語の基本 — 尊敬語・謙譲語・丁寧語の使い分け",{"articleId":385,"path":386,"title":387},"law-keihin-hyouji","\u002Farticles\u002Flaw\u002Fkeihin-hyouji","改正景品表示法とステマ規制 — マーケティングの法的注意点",{"articleId":389,"path":390,"title":391},"living-kenkou-hoken","\u002Farticles\u002Fliving-in-japan\u002Fkenkou-hoken","健康保険の入門 — 国保と社保の違い",{"articleId":393,"path":394,"title":395},"living-kosei-nenkin","\u002Farticles\u002Fliving-in-japan\u002Fkosei-nenkin","厚生年金と国民年金 — 老後の備えと現役の負担",{"articleId":397,"path":398,"title":399},"tech-line-llmops","\u002Farticles\u002Ftech\u002Fline-llmops","LINEのLLMOps — 大規模言語モデル運用の取り組み",{"articleId":401,"path":402,"title":403},"tech-line-streaming","\u002Farticles\u002Ftech\u002Fline-streaming","LINEの大規模リアルタイム配信基盤",{"articleId":405,"path":406,"title":407},"living-chintai-keiyaku","\u002Farticles\u002Fliving-in-japan\u002Fliving-chintai-keiyaku","賃貸契約と保証会社 — 礼金・敷金から保証料まで",{"articleId":409,"path":410,"title":411},"living-eijuken","\u002Farticles\u002Fliving-in-japan\u002Fliving-eijuken","永住権申請の最新基準 — 一般・高度専門職ルート比較",{"articleId":413,"path":414,"title":415},"living-engineer-visa","\u002Farticles\u002Fliving-in-japan\u002Fliving-engineer-visa","エンジニアの在留資格 — 「技術・人文知識・国際業務」ビザの取得手順",{"articleId":417,"path":418,"title":419},"living-ginkou-koza","\u002Farticles\u002Fliving-in-japan\u002Fliving-ginkou-koza","銀行口座開設とクレジットカード — 外国人エンジニアの実務",{"articleId":421,"path":422,"title":423},"living-hikkoshi-checklist","\u002Farticles\u002Fliving-in-japan\u002Fliving-hikkoshi-checklist","引越し手続きチェックリスト — 役所・ライフライン・住所変更",{"articleId":425,"path":426,"title":427},"living-koudo-senmon","\u002Farticles\u002Fliving-in-japan\u002Fliving-koudo-senmon","高度専門職ビザの実務 — ポイント制度と特権",{"articleId":429,"path":430,"title":431},"culture-matsuri","\u002Farticles\u002Fculture\u002Fmatsuri","日本の祭り — 季節と地域の象徴",{"articleId":433,"path":434,"title":435},"bj-meishi-koukan","\u002Farticles\u002Fbusiness-japanese\u002Fmeishi-koukan","名刺交換の作法 — 第一印象を決める数十秒",{"articleId":437,"path":438,"title":439},"tech-mercari-merpay-id","\u002Farticles\u002Ftech\u002Fmercari-merpay-id","メルペイのID基盤 — eKYC・本人確認の技術",{"articleId":441,"path":442,"title":443},"tech-mercari-microservices","\u002Farticles\u002Ftech\u002Fmercari-microservices-migration","Mercariのマイクロサービス移行 — モノリスから次世代へ",{"articleId":445,"path":446,"title":447},"tech-mf-multitenant","\u002Farticles\u002Ftech\u002Fmoneyforward-multitenant-saas","Money Forwardのマルチテナント設計 — データ分離とセキュリティ",{"articleId":449,"path":450,"title":451},"bj-nemawashi-ringi","\u002Farticles\u002Fbusiness-japanese\u002Fnemawashi-ringi","根回しと稟議 — 日本企業の意思決定の仕組み",{"articleId":453,"path":454,"title":455},"living-nenmatsu-chousei","\u002Farticles\u002Fliving-in-japan\u002Fnenmatsu-chousei","年末調整の仕組み — 会社員のための税精算",{"articleId":457,"path":458,"title":459},"bj-1on1","\u002Farticles\u002Fbusiness-japanese\u002Fone-on-one","1on1ミーティングの活用法 — 上司と部下の対話",{"articleId":461,"path":462,"title":463},"bj-online-kaigi","\u002Farticles\u002Fbusiness-japanese\u002Fonline-kaigi","オンライン会議のエチケット — Zoom時代のビジネスマナー",{"articleId":465,"path":466,"title":467},"culture-onsen","\u002Farticles\u002Fculture\u002Fonsen","温泉文化と入浴マナー — 名湯巡りの楽しみ方",{"articleId":469,"path":470,"title":471},"culture-pro-baseball","\u002Farticles\u002Fculture\u002Fpro-baseball","プロ野球と高校野球 — 国民的スポーツの二つの顔",{"articleId":473,"path":474,"title":475},"culture-ramen","\u002Farticles\u002Fculture\u002Framen","ラーメン地域ごとの違い — 札幌・博多・喜多方",{"articleId":477,"path":478,"title":479},"tech-recruit-data-platform","\u002Farticles\u002Ftech\u002Frecruit-data-platform","Recruit データ基盤刷新事例 — 数十サービスの統合",{"articleId":481,"path":482,"title":483},"law-roukikihou-kihon","\u002Farticles\u002Flaw\u002Froukikihou-kihon","労働基準法の基本 — 労働時間・休憩・残業規制",{"articleId":485,"path":486,"title":487},"culture-sado","\u002Farticles\u002Fculture\u002Fsado","茶道入門 — 千利休と侘び寂びの精神",{"articleId":489,"path":490,"title":491},"culture-sandou","\u002Farticles\u002Fculture\u002Fsandou","茶華書三道 — 日本の精神を体現する三つの道",{"articleId":493,"path":494,"title":495},"culture-seasonal-events","\u002Farticles\u002Fculture\u002Fseasonal-events","季節の行事 — 正月から年末まで日本の年中行事",{"articleId":497,"path":498,"title":499},"exam-sg","\u002Farticles\u002Fexams\u002Fsg","情報セキュリティマネジメント試験 — 管理者向けセキュリティ",{"articleId":501,"path":502,"title":503},"bj-shagai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshagai-mail","社外メールの書き方 — お詫び・依頼・確認",{"articleId":505,"path":506,"title":507},"bj-shanai-mail","\u002Farticles\u002Fbusiness-japanese\u002Fshanai-mail","社内メールの書き方 — 件名から結びまで",{"articleId":509,"path":510,"title":511},"culture-sumo","\u002Farticles\u002Fculture\u002Fsumo","大相撲 — 番付と力士の生活",{"articleId":513,"path":514,"title":515},"culture-sushi","\u002Farticles\u002Fculture\u002Fsushi","寿司の歴史と種類 — なれずしから江戸前まで",{"articleId":517,"path":518,"title":519},"culture-washoku","\u002Farticles\u002Fculture\u002Fwashoku","和食 — ユネスコ無形文化遺産と一汁三菜",{"articleId":521,"path":522,"title":523},"law-yuukyuu-kyuuka","\u002Farticles\u002Flaw\u002Fyuukyuu-kyuuka","有給休暇の取得ルールと最新改正",{"articleId":525,"path":526,"title":527},"kjh-k1-h04-anzen-kanri","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fanzen-kanri","課題Ⅰ 第４編① 個人データに関する義務 ― 正確性の確保・安全管理措置・漏えい報告",{"articleId":529,"path":530,"title":531},"bill-one-auth","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fbill-one-auth","インボイス管理サービスBill Oneの認証を内製認証基盤に置き換えて認証基盤のコストを削減した話",{"articleId":533,"path":534,"title":535},"contract-one-vision","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fcontract-one-vision","契約書を\"意思決定のインフラ\"に──Contract Oneで挑む、新たな価値創造",{"articleId":537,"path":538,"title":539},"kjh-k1-h04-daisan-sha-teikyou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fdaisan-sha-teikyou","課題Ⅰ 第４編② 第三者提供の制限 ― 同意・オプトアウト・非該当類型",{"articleId":541,"path":542,"title":543},"eight-web-renewal","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Feight-web-renewal","Web版Eightのリニューアルと、安全なリリースのための取り組み",{"articleId":545,"path":546,"title":547},"kjh-k1-h04-gaikoku-kiroku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fgaikoku-kiroku","課題Ⅰ 第４編③ 外国にある第三者への提供の制限・記録義務・確認義務（法28条〜30条）",{"articleId":549,"path":550,"title":551},"kjh-k2-h04-gijutsu-jisshi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-jisshi","課題Ⅱ 第４編② 技術的安全管理措置の実施項目",{"articleId":553,"path":554,"title":555},"kjh-k2-h04-gijutsu-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fgijutsu-kiso","課題Ⅱ 第４編① 技術的セキュリティ対策の基礎知識",{"articleId":557,"path":558,"title":559},"kjh-k1-h01-hotaikei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhotaikei","課題Ⅰ 第１編 個人情報保護の法体系と各種認定制度",{"articleId":561,"path":562,"title":563},"kjh-k1-h06-hoyu-data","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fhoyu-data","課題Ⅰ 第６編 保有個人データに関する義務",{"articleId":565,"path":566,"title":567},"kjh-k1-h07-kamei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkamei-kakou","課題Ⅰ 第７編 仮名加工情報（法41条・42条）",{"articleId":569,"path":570,"title":571},"kjh-k1-h05-kanren-joho","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkanren-joho","課題Ⅰ 第５編 個人関連情報に関する義務（法31条）",{"articleId":573,"path":574,"title":575},"kjh-k1-h02-kihon-rinen","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkihon-rinen","課題Ⅰ 第２編 個人情報保護法の目的・基本理念と用語の定義",{"articleId":577,"path":578,"title":579},"kjh-k1-h09-jikkousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h09-jikkousei","課題Ⅰ 第９編 実効性を担保する仕組み等",{"articleId":581,"path":582,"title":583},"kjh-k1-h10-gyousei","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h10-gyousei","課題Ⅰ 第10編 行政機関等における個人情報等の取扱い",{"articleId":585,"path":586,"title":587},"kjh-k1-h11-my-number-hogo","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-hogo","課題Ⅰ 第11編② マイナンバー法 ― 特定個人情報の提供制限・保護・監督・罰則（法19条〜57条）",{"articleId":589,"path":590,"title":591},"kjh-k1-h11-my-number-sousoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Fkjh-k1-h11-my-number-sousoku","課題Ⅰ 第11編① マイナンバー法 ― 総則・個人番号・個人番号カード（法1条〜18条の5）",{"articleId":593,"path":594,"title":595},"kjh-k2-h01-guideline","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-guideline","課題Ⅱ 第１編② セキュリティ対策基準とガイドライン",{"articleId":597,"path":598,"title":599},"kjh-k2-h01-security-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h01-security-kiso","課題Ⅱ 第１編① 情報セキュリティの基礎と脅威",{"articleId":601,"path":602,"title":603},"kjh-k2-h02-anzen-kanri-sochi","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-anzen-kanri-sochi","課題Ⅱ 第２編② 組織的・人的セキュリティ ― 安全管理措置・委託先監督・事故対応",{"articleId":605,"path":606,"title":607},"kjh-k2-h02-soshiki-kiso","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Fkjh-k2-h02-soshiki-kiso","課題Ⅱ 第２編① 組織的・人的セキュリティ ― 基本方針の策定からリスク管理・規程整備まで",{"articleId":609,"path":610,"title":611},"kjh-k2-h03-office","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-2\u002Foffice","課題Ⅱ 第３編 オフィスセキュリティ",{"articleId":613,"path":614,"title":615},"kjh-k1-h03-riyou-mokuteki","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Friyou-mokuteki","課題Ⅰ 第３編① 利用目的の特定・変更と利用目的による制限、不適正な利用の禁止",{"articleId":617,"path":618,"title":619},"sansan-data-intelligence","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-data-intelligence","Sansan Data Intelligenceリリースに寄せて",{"articleId":621,"path":622,"title":623},"sansan-engineer-team-infra","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-engineer-team-infra","Sansan Engineer Team：インフラ戦略部",{"articleId":625,"path":626,"title":627},"sansan-honne-15","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-honne-15","入社後のホンネ［技術本部 データ戦略部 Infrastructureグループ 渡邉 友］",{"articleId":629,"path":630,"title":631},"sansan-interview-110","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-110","SIer出身者が活躍する理由とは。Sansanを牽引するプロダクト開発に挑み続ける",{"articleId":633,"path":634,"title":635},"sansan-interview-126","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-126","AIと協働する開発組織、そして技術の深化。Sansan 新CTO笹川が語るビジョン",{"articleId":637,"path":638,"title":639},"sansan-interview-127","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-127","Sansanの技術基盤を関西から築く。新設組織で未来を創る、エンジニアの挑戦",{"articleId":641,"path":642,"title":643},"sansan-interview-130","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-130","Sansanの全社基盤を支えるPlatform Engineering Unitの挑戦",{"articleId":645,"path":646,"title":647},"sansan-interview-40","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-interview-40","膨大な量のデータを平然と処理する。Sansanのインフラのすごさが、そこに表れている。",{"articleId":649,"path":650,"title":651},"sansan-oyaco","\u002Farticles\u002Fsoftware%2Fcompanies%2Fsansan\u002Fsansan-oyaco","仕事と子育ての両立を支援する制度「OYACO」",{"articleId":653,"path":654,"title":655},"kjh-k1-h03-tekisei-shutoku","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftekisei-shutoku","課題Ⅰ 第３編② 適正な取得・要配慮個人情報・利用目的の通知",{"articleId":657,"path":658,"title":659},"kjh-k1-h08-tokumei-kakou","\u002Farticles\u002Fkojin-joho-hogo%2Fkadai-1\u002Ftokumei-kakou","課題Ⅰ 第８編 匿名加工情報に関する義務等（法43条〜46条）"]