题库练习
系统集成项目管理工程师题库:章节练习、模拟考试与错题本,与考点精讲章节联动。
题库由浏览器端实时渲染:章节练习逐题作答即时判分看解析;模拟考试随机抽题限时自测;答错的题自动进错题本(保存在本机浏览器)。每道题解析中的「回看考点」可直接跳到书中对应章节。
当前题库为骨架示例(每章数题),正式扩充后按章节/来源/难度自由筛选。
{"bank":[{"analysis":"国家信息化体系六要素(官方教程口径):信息资源、信息网络、信息技术应用、信息技术与产业、信息化人才、信息化政策法规与标准规范。题干为『选非题』,只有『信息化运营外包』不在六要素之列。","answer":"D","chapter":"信息化与系统集成技术","difficulty":1,"explain":{"A":"信息资源是六要素之一(且常被视为信息化建设的核心资源),本题要选『不属于』的一项,故排除。","B":"信息网络属于六要素范畴,是信息化建设的物理基础,不能选。","C":"信息化人才是六要素之一,没有人才信息化无法持续,故排除。"},"id":"rk-zhishi-ch01-001","options":["信息资源","信息网络","信息化人才","信息化运营外包"],"source":"chapter","stem":"根据国家信息化体系的常见划分,下列选项中**不属于**六要素之一的是?","subject":"综合知识","type":"single"},{"analysis":"规划阶段回答『做什么、值不值得做』(立项与可行性);设计阶段回答『怎么做』;实施阶段把设计变成现实;运维阶段保障上线后的稳定运行。题干关键词『做什么』对应规划阶段。","answer":"A","chapter":"信息化与系统集成技术","difficulty":1,"explain":{"B":"设计阶段解决的是『怎么做』——架构、数据库、接口与界面设计,前提是需求已经明确,不能回答『做什么』。","C":"实施阶段是把设计方案编码实现、测试部署,属于动作执行阶段,晚于需求定义。","D":"运维阶段保障已上线系统的运行与变更,位于生命周期最末端,与需求定义无关。"},"id":"rk-zhishi-ch01-002","options":["系统规划","系统设计","系统实施","系统运维"],"source":"chapter","stem":"信息系统生命周期中,『明确系统要做什么、解决哪些问题』通常属于哪个阶段的任务?","subject":"综合知识","type":"single"},{"analysis":"SOA 的核心思想:把业务能力封装为『服务』,通过标准接口(如 Web Service)暴露,服务间松耦合、可组合复用。它不是把系统物理合并,也不是只做硬件网络层面的集成。","answer":"B","chapter":"信息化与系统集成技术","difficulty":2,"explain":{"A":"SOA 追求的是逻辑上的服务化与松耦合,让系统通过服务协作,而非把系统物理合并成一个大单体。","C":"SOA 属于应用层/数据层的集成思想,网络集成只是底层的技术支撑之一,不能以偏概全。","D":"恰好相反——采用 SOA 正是为了让原本孤立、异构的系统之间能够协同集成,集成仍然是必须的。"},"id":"rk-zhishi-ch01-003","options":["SOA 要求把各系统完全合并为一个大系统","SOA 通过标准化服务接口实现松耦合与复用","SOA 只适用于硬件层面的网络集成","采用 SOA 后系统之间不再需要任何集成"],"source":"chapter","stem":"关于面向服务架构(SOA),下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"保密性(Confidentiality)指信息不被未授权者获取。内部员工向竞争对手外发机密文档,使信息泄露给未授权方,直接破坏保密性。","answer":"A","chapter":"信息化与系统集成技术","difficulty":2,"explain":{"B":"篡改数据破坏的是完整性(Integrity)——信息被非法修改,与『泄露给未授权者』的保密性问题不同。","C":"DDoS 导致业务中断破坏的是可用性(Availability)——授权用户无法正常访问服务。","D":"删除日志破坏的是完整性/可审计性,旨在消灭操作痕迹,属于完整性范畴而非保密性。"},"id":"rk-zhishi-ch01-004","options":["内部员工将研发机密文档外发给竞争对手","攻击者篡改公司官网的商品价格","服务器遭受 DDoS 攻击导致网站无法访问","系统操作日志被非法删除以掩盖操作痕迹"],"source":"chapter","stem":"下列情形中,最直接破坏信息安全『保密性』的是?","subject":"综合知识","type":"single"},{"analysis":"项目三大特征:临时性(有明确起止)、独特性(成果独一无二)、渐进明细(随进展不断细化)。『重复循环』是持续运营的特征,与项目相对。","answer":"D","chapter":"项目管理基础","difficulty":1,"explain":{"A":"临时性是项目特征——项目有明确的开始与结束,题干要求选『不是』项目特征的,故排除。","B":"独特性是项目特征——没有两个完全相同的项目,不能选。","C":"渐进明细是项目特征——项目目标与方案随推进逐步细化,同样不能选。"},"id":"rk-zhishi-ch02-001","options":["临时性","独特性","渐进明细","重复循环性"],"source":"chapter","stem":"下列哪项**不是**项目的典型特征?","subject":"综合知识","type":"single"},{"analysis":"五大过程组:启动 → 规划 → 执行 → 监控 → 收尾。监控贯穿执行全程但排序固定:没有启动授权就没有规划,没有规划就无法执行。","answer":"A","chapter":"项目管理基础","difficulty":1,"explain":{"B":"规划必须发生在启动(获得授权)之后;收尾是最后一道程序,监控在其前而非其后。","C":"顺序错误:规划应先于执行,不能先执行后规划。","D":"顺序错误:启动在最前(先授权立项),规划在启动之后、执行之前。"},"id":"rk-zhishi-ch02-002","options":["启动—规划—执行—监控—收尾","规划—启动—执行—收尾—监控","启动—执行—规划—监控—收尾","规划—执行—启动—监控—收尾"],"source":"chapter","stem":"项目管理五大过程组的正确顺序是?","subject":"综合知识","type":"single"},{"analysis":"十大知识领域:整合、范围、进度、成本、质量、资源、沟通、风险、采购、干系人管理。『文档管理』不是独立的知识领域——文档产出分散在各过程组中管理。","answer":"C","chapter":"项目管理基础","difficulty":2,"explain":{"A":"风险管理是十大知识领域之一,负责识别、分析与应对不确定性,不能选。","B":"干系人管理是第十大知识领域,负责识别并管理受项目影响或影响项目的个人与组织,不能选。","D":"整合管理居十大领域之首,负责协调全局、平衡各方约束(题干是选非题,此项应排除)。"},"id":"rk-zhishi-ch02-003","options":["风险管理","干系人管理","文档管理","整合管理"],"source":"chapter","stem":"下列领域中,**不属于**项目管理十大知识领域的是?","subject":"综合知识","type":"single"},{"analysis":"项目章程由发起人/高层签发,正式授权项目启动并任命项目经理,给出高层级目标与约束;后续范围仍须通过变更控制管理,并非永久冻结。","answer":"B","chapter":"项目管理基础","difficulty":2,"explain":{"A":"项目经理可参与章程的起草与输入,但签发权在发起人/高层——自行签发缺少组织授权,不成立。","C":"章程只是『授权 + 高层级目标』的起点,后续范围变更仍要通过变更控制流程处理,不能说范围从此固定。","D":"章程在启动过程组就要产出,是项目启动的『出生证』,收尾阶段早已不需要签发。"},"id":"rk-zhishi-ch02-004","options":["由项目经理编制并自行签发","由项目发起人或高层管理者签发,正式授权项目启动","章程批准后项目范围就完全固定,不能再变更","章程只在项目收尾时才需要"],"source":"chapter","stem":"关于项目章程,下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"WBS 以『可交付成果』为导向逐层分解到工作包,遵循 100% 规则:底层工作包之和必须覆盖且不超出全部项目范围。它是范围管理的核心工具,后续通过变更控制可调整。","answer":"B","chapter":"范围与进度管理","difficulty":2,"explain":{"A":"WBS 分解的对象是项目范围与可交付成果(工作包);把工作包再细化为活动属于进度管理范畴,WBS 本身不以活动为对象。","C":"分解过粗的工作包难以估算、分配与监控;WBS 应分解到『可管理、可估算』的粒度,并非越粗越好。","D":"WBS 基线建立后若需调整,应通过正式的变更控制流程,而非『禁止修改』。"},"id":"rk-zhishi-ch03-001","options":["WBS 只分解进度活动,不涉及可交付成果","WBS 底层分解之和应等于 100% 的项目范围(100% 规则)","WBS 分解得越粗越好,便于灵活调整","WBS 一旦建立就禁止修改"],"source":"chapter","stem":"关于 WBS(工作分解结构)的说法,正确的是?","subject":"综合知识","type":"single"},{"analysis":"关键路径=网络图中最长路径=总浮动时间最小(通常为 0)的路径,决定项目最短工期;当多条路径总浮动并列最小时,项目存在多条关键路径。","answer":"B","chapter":"范围与进度管理","difficulty":2,"explain":{"A":"浮动时间最长意味着『最不紧张』,恰恰相反,关键路径是最紧张(总浮动最小)的那条。","C":"当多条路径共享最小浮动时,项目可同时存在多条关键路径,不是只能有一条。","D":"关键路径决定项目工期(进度),与成本没有定义上的直接关系。"},"id":"rk-zhishi-ch03-002","options":["关键路径是浮动时间最长的路径","关键路径上的活动总浮动时间最小(通常为零),且决定项目最短工期","一个项目只能存在一条关键路径","关键路径只与成本有关,与工期无关"],"source":"chapter","stem":"关于网络图中的关键路径,下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"赶工=通过增加资源(人手/加班)压缩关键路径活动的历时,代价通常是成本上升;只有压缩关键路径活动才能缩短总工期。","answer":"B","chapter":"范围与进度管理","difficulty":3,"explain":{"A":"快速跟进是把原本串行的活动改为并行执行,靠改变逻辑关系省时间,主要风险是返工;题干描述的是『增加人手』,不是改并行。","C":"资源平滑是在不改变工期的前提下调整资源使用峰谷,不能缩短总工期,与『赶进度』目标不符。","D":"范围缩减要通过范围变更减少交付内容,题干并未提及削减范围。"},"id":"rk-zhishi-ch03-003","options":["快速跟进(并行执行)","赶工(crashing)","资源平滑","范围缩减"],"source":"chapter","stem":"项目进度滞后,项目经理决定在关键路径活动上增加人手加班赶工。这种做法属于?","subject":"综合知识","type":"single"},{"analysis":"A 完成于第 3 天;B 完成于第 8 天、C 完成于第 7 天;D 需 B、C 均完成,故最早第 8 天开始,第 10 天完成。路径 A→B→D=3+5+2=10 天为最长路径(关键路径),C 所在路径 A→C→D=9 天,有 1 天浮动。","answer":"A","chapter":"范围与进度管理","difficulty":3,"explain":{"B":"A→C→D=3+4+2=9 天,比 A→B→D 短,且 C 有 1 天浮动,不是关键路径。","C":"A→B→D 的历时应为 3+5+2=10 天;8 天漏算了 D 的历时(3+5=8 只是 B 的完成时刻)。","D":"C 与 B 是并行关系,D 前的两条前导路径互不串行,不存在 A→C→B→D 这种链路。"},"id":"rk-zhishi-ch03-004","options":["关键路径 A→B→D,总工期 10 天","关键路径 A→C→D,总工期 9 天","关键路径 A→B→D,总工期 8 天","关键路径 A→C→B→D,总工期 12 天"],"source":"chapter","stem":"某项目网络计划(历时单位:天):活动 A 开工即开始、历时 3;A 完成后,B(历时 5)与 C(历时 4)并行开始;活动 D(历时 2)须在 B、C 均完成后开始。该项目关键路径与总工期是?","subject":"综合知识","type":"single"},{"analysis":"CV=EV−AC=90−110=−20 万元<0 → 成本超支;SV=EV−PV=90−100=−10 万元<0 → 进度落后。","answer":"B","chapter":"成本与质量管理","difficulty":3,"explain":{"A":"成本并未节约:AC(110)已大于 EV(90),CV 为负;进度也未超前,SV 为负。","C":"进度并未超前:EV(90)小于 PV(100),实际完成的计划价值低于计划,SV 为负说明落后。","D":"成本并未节约:实际花费 AC 超出挣值 EV 达 20 万元,方向判断反了。"},"id":"rk-zhishi-ch04-001","options":["成本节约且进度超前","成本超支且进度落后","成本超支但进度超前","成本节约但进度落后"],"source":"chapter","stem":"检查点数据:PV=100 万元,EV=90 万元,AC=110 万元。关于项目当前状态,下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"SPI=EV/PV。SPI>1 表示挣值大于计划价值——实际完成进度超前于计划;SPI 只反映进度绩效,不直接度量成本。","answer":"C","chapter":"成本与质量管理","difficulty":2,"explain":{"A":"SPI>1 意味着 EV>PV,即『干得比计划多』,是进度超前而非落后。","B":"SPI 分子分母都是价值量(EV、PV),不含实际成本 AC,无法得出成本结论;要看成本需用 CPI。","D":"SPI 只描述到检查点为止的进度绩效,1.2 表示超前,但不代表工作已全部完成(EV 仍小于 BAC)。"},"id":"rk-zhishi-ch04-002","options":["项目进度落后于计划","项目成本超支","项目实际完成的进度价值高于计划价值,进度超前","项目已完成全部工作"],"source":"chapter","stem":"某项目 SPI(进度绩效指数)为 1.2,其含义是?","subject":"综合知识","type":"single"},{"analysis":"QA 面向『过程』、重在预防,典型手段是过程审计(审计是否按流程规范执行);QC 面向『结果』,通过检验测量发现问题并纠正。","answer":"B","chapter":"成本与质量管理","difficulty":2,"explain":{"A":"抽样检验是对产出结果的测量验证,属于质量控制(QC)活动。","C":"返工是针对已发现缺陷的纠正执行,属于 QC 结果处理环节,不是过程保证。","D":"验收测试面向最终交付成果的符合性检查,属 QC/验收范畴。"},"id":"rk-zhishi-ch04-003","options":["对交付物进行抽样检验","执行过程审计,确认过程按规范执行","对发现的缺陷进行返工","组织客户做验收测试"],"source":"chapter","stem":"下列活动属于质量保证(QA)的是?","subject":"综合知识","type":"single"},{"analysis":"CPI=EV/AC=80/100=0.8。典型偏差下 EAC=BAC/CPI=200/0.8=250 万元,即按当前『每花 1 元只产出 0.8 元价值』的效率做完整个项目需要 250 万元。","answer":"C","chapter":"成本与质量管理","difficulty":3,"explain":{"A":"200 万元等于 BAC,前提是成本绩效无偏差(CPI=1),与本题当前 CPI=0.8 矛盾。","B":"220 万元是『非典型偏差』的算法:EAC=AC+(BAC−EV)=100+120=220,假设当前超支是一次性的、后续不再发生;题干明确按典型偏差继续。","D":"300 万元没有计算依据:BAC/CPI=200/0.8=250,而非 300。"},"id":"rk-zhishi-ch04-004","options":["200","220","250","300"],"source":"chapter","stem":"某项目 BAC=200 万元。检查时 EV=80 万元、AC=100 万元。若剩余工作按当前成本绩效指数(典型偏差)继续,完工估算 EAC 为多少万元?","subject":"综合知识","type":"single"},{"analysis":"转移=把风险后果连同应对责任转给第三方,典型手段是购买保险、外包、担保等。保险不降低事故发生概率,但把损失的经济后果转移给了保险公司。","answer":"B","chapter":"风险与干系人管理","difficulty":1,"explain":{"A":"规避是改变计划以消除威胁本身(如改用不易损毁的设备方案),使风险不发生;买保险并未消除设备损毁的可能。","C":"减轻是主动降低风险的发生概率或影响(如加装保护装置、定期巡检);保险不改变概率与影响,只转移损失承担。","D":"接受是自留风险(主动预留储备或被动承担),与『把风险转给保险公司』的意图相反。"},"id":"rk-zhishi-ch05-001","options":["规避","转移","减轻","接受"],"source":"chapter","stem":"为应对设备损毁风险,项目组为关键设备购买保险。该做法属于哪种风险应对策略?","subject":"综合知识","type":"single"},{"analysis":"定性风险分析对每个已识别风险按发生概率与影响的主观评级(结合矩阵)排出优先级,速度快、适合先做;定量分析才用数值模型量化总体影响。","answer":"B","chapter":"风险与干系人管理","difficulty":2,"explain":{"A":"定量风险分析用期望货币值 EMV、决策树、蒙特卡洛模拟等数值方法量化风险对目标的总体影响,不只做评级排序。","C":"风险审计是检查风险管理过程及其有效性,属于监控过程组的活动,不是风险分析方法。","D":"敏感性分析是定量分析的一种技术(找出对结果影响最大的变量),题干描述的是矩阵评级,属定性。"},"id":"rk-zhishi-ch05-002","options":["定量风险分析","定性风险分析","风险审计","敏感性分析"],"source":"chapter","stem":"使用『概率 × 影响矩阵』对风险进行评级与排序,属于哪种风险分析?","subject":"综合知识","type":"single"},{"analysis":"权力—利益方格:高权力+高利益→重点管理;高权力+低利益→令其满意;低权力+高利益→随时告知(保持其知情与支持);低权力+低利益→监督。题干为低权力高利益,对应『随时告知』。","answer":"A","chapter":"风险与干系人管理","difficulty":2,"explain":{"B":"『令其满意』对应的是高权力+低利益的干系人(权力大但不关心日常细节,重点维护其态度),与题干权力低不符。","C":"『重点管理』适用于权力与利益双高的核心干系人,题干权力低,达不到重点管理的匹配条件。","D":"『监督』适用于权力、利益双低的干系人;本题对象利益高,需主动告知,不能只作旁观式监督。"},"id":"rk-zhishi-ch05-003","options":["随时告知","令其满意","重点管理","仅作监督"],"source":"chapter","stem":"某干系人对项目利益(影响)高、但权力低。依据『权力—利益』方格,宜采取的管理策略是?","subject":"综合知识","type":"single"},{"analysis":"EMV=概率 × 影响=30% × 50=15 万元(期望损失)。EMV 用于定量风险分析中比较不同应对方案或风险大小的期望值。","answer":"B","chapter":"风险与干系人管理","difficulty":2,"explain":{"A":"50 万元是风险『一旦发生』的损失额,没有乘以发生概率,混淆了影响值与期望值。","C":"1.5 万元是把概率错算为 3%(50×0.03),30% 应写作 0.3。","D":"35 万元是把未发生概率 70% 与损失额相乘(50×0.7)的误算,期望值应乘的是发生概率。"},"id":"rk-zhishi-ch05-004","options":["损失 50 万元","期望损失 15 万元","期望损失 1.5 万元","损失 35 万元"],"source":"chapter","stem":"某风险事件发生概率为 30%,一旦发生将造成 50 万元损失;不发生则无损失。该风险的期望货币值(EMV,按损失计)约为?","subject":"综合知识","type":"single"},{"analysis":"RACI 四角色:R(Responsible)负责执行;A(Accountable)最终批准并对结果负总责,每项工作只能有唯一的 A;C(Consulted)被咨询;I(Informed)被知会。","answer":"B","chapter":"资源与沟通管理","difficulty":2,"explain":{"A":"『负责执行』是 R(Responsible)的含义,题干问的是 A。","C":"『提供咨询』是 C(Consulted),不是 A。","D":"『只需知会』是 I(Informed),A 需要拍板担责。"},"id":"rk-zhishi-ch06-001","options":["负责执行具体工作","最终拍板、对结果负总责","提供咨询意见","只需事后知会"],"source":"chapter","stem":"责任分配矩阵(RACI)中,字母 A(Accountable)通常表示?","subject":"综合知识","type":"single"},{"analysis":"妥协(调解)=双方各让一步达成折中;注意『合作/面对』是不让步、共同寻找双赢新方案的更高层次做法。","answer":"C","chapter":"资源与沟通管理","difficulty":2,"explain":{"A":"撤退/回避是对冲突不处理或拖延,与题干『协调折中』不符。","B":"缓和/包容强调求同存异、弱化分歧,而不是各让一部分形成新方案。","D":"强迫/命令是以权力压人、赢—输结局,题中是双方主动让步。"},"id":"rk-zhishi-ch06-002","options":["撤退/回避","缓和/包容","妥协/调解","强迫/命令"],"source":"chapter","stem":"两位工程师就接口方案争执不下,项目经理协调双方各自放弃部分立场、形成折中方案。该做法属于哪种冲突处理策略?","subject":"综合知识","type":"single"},{"analysis":"沟通渠道数=N(N−1)/2:8 人=28 条,10 人=45 条,增加 45−28=17 条。","answer":"B","chapter":"资源与沟通管理","difficulty":3,"explain":{"A":"2 是人数增量,不是渠道数量增量(渠道随人数平方级增长)。","C":"36 是 9 人的渠道数(9×8/2),与题意 8→10 不符。","D":"45 是 10 人的渠道总数,题干问的是『增加了多少条』,要再减去 28。"},"id":"rk-zhishi-ch06-003","options":["2","17","36","45"],"source":"chapter","stem":"某项目干系人(含项目组成员)由 8 人增加到 10 人,沟通渠道数量增加了多少条?","subject":"综合知识","type":"single"},{"analysis":"形成期特征:成员相互试探、依赖领导、目标与角色未定;随后依次经历震荡(冲突)、规范(协作成型)、成熟(高效默契),项目结束解散。","answer":"A","chapter":"资源与沟通管理","difficulty":1,"explain":{"B":"震荡期以分歧、角色竞争和冲突为特征,题干是『客气试探』,尚未到冲突阶段。","C":"规范期已立好规矩、能够协作,与刚组建的状态不符。","D":"成熟期团队高效默契、自主运转,是后期状态。"},"id":"rk-zhishi-ch06-004","options":["形成期","震荡期","规范期","成熟期"],"source":"chapter","stem":"项目团队刚组建,成员彼此客气试探,对项目目标和各自角色还不明确。团队最可能处于哪个发展阶段?","subject":"综合知识","type":"single"},{"analysis":"固定总价合同一口价成交,成本超支风险由卖方承担,买方风险最小;这也是买方偏好总价合同的原因。","answer":"B","chapter":"采购与合同管理","difficulty":1,"explain":{"A":"总价合同正是为了把成本风险转移给卖方,买方不再为超支买单。","C":"除非采用总价加激励(FPIF)并按约定分成,否则不存在均摊机制。","D":"监理方负责监督履约,不承担合同成本风险。"},"id":"rk-zhishi-ch07-001","options":["买方(甲方)","卖方(承包方)","双方均摊","监理方"],"source":"chapter","stem":"采用固定总价合同(FFP)时,若项目实施实际成本超过合同总价,超支部分通常由谁承担?","subject":"综合知识","type":"single"},{"analysis":"范围不明时难以事先定死总价,也不宜让卖方背过大成本风险;工料合同按固定单价×实际工作量结算,适合范围模糊或紧急启动的工作(示例口径)。","answer":"C","chapter":"采购与合同管理","difficulty":2,"explain":{"A":"FFP 要求范围相对明确才能合理定价,范围不清时盲目定总价极易引发争议。","B":"成本类合同仍需要能界定大致范围并实报实销,对『需求不清、快速启动』的临时性工作,工料合同更贴合。","D":"CPPC 让卖方『花得越多赚得越多』,激励超支,应避免使用。"},"id":"rk-zhishi-ch07-002","options":["固定总价合同(FFP)","成本加固定酬金合同(CPFF)","工料合同(T\u0026M)","成本加成本百分比合同(CPPC)"],"source":"chapter","stem":"项目需求尚不清晰,又需要尽快启动某项外包工作。此时较适宜选用的合同类型是?","subject":"综合知识","type":"single"},{"analysis":"邀请招标应邀请 3 家及以上;5 人以上单数且技术经济专家不少于 2/3 是评标委员会的组成要求,别把两组数字记混。","answer":"B","chapter":"采购与合同管理","difficulty":1,"explain":{"A":"2 家低于法定下限,不具备充分竞争性。","C":"5 是评标委员会人数的下限(且须单数),不是邀请对象数量。","D":"7 无依据,属干扰项。"},"id":"rk-zhishi-ch07-003","options":["2 家","3 家","5 家","7 家"],"source":"chapter","stem":"依招标投标相关法规(示例口径),采用邀请招标时,应当向多少家以上具备承担招标项目能力的特定法人或其他组织发出投标邀请书?","subject":"综合知识","type":"single"},{"analysis":"开发库供开发人员日常读写(动态);受控库存放评审通过、形成基线的配置项,受权限控制;产品库存放正式发布/交付的版本,只读。","answer":"B","chapter":"文档、配置与变更管理","difficulty":2,"explain":{"A":"开发库是动态工作区,开发人员可随意更改,尚未受控。","C":"产品库是正式发布的只读版本,与『形成基线、需权限』的受控库不同。","D":"备份库不属于配置管理标准三库。"},"id":"rk-zhishi-ch08-001","options":["开发库","受控库(主库)","产品库(发布库)","备份库"],"source":"chapter","stem":"配置管理『三库』中,存放经评审、形成基线的内容且访问需权限控制的库是?","subject":"综合知识","type":"single"},{"analysis":"标准流程:先登记变更请求 CR,再做影响分析,重要变更经 CCB 审批,批准后实施并同步更新计划/配置/文档,最后验证结果并关闭变更。","answer":"B","chapter":"文档、配置与变更管理","difficulty":2,"explain":{"A":"影响分析应在变更请求登记之后进行,顺序颠倒。","C":"审批在后、请求在前,先审后提完全颠倒。","D":"『先斩后奏』违反变更控制原则,未经批准的变更不得实施。"},"id":"rk-zhishi-ch08-002","options":["影响分析→提交变更请求→CCB 审批→实施","登记变更请求→影响分析→CCB 审批→实施并更新配置→验证关闭","CCB 审批→提交变更请求→影响分析→实施","先实施→事后补交请求→CCB 追认"],"source":"chapter","stem":"项目收到一项变更请求后,正确的处理顺序是?","subject":"综合知识","type":"single"},{"analysis":"功能配置审计核对功能与需求的一致性;物理配置审计核对交付物与配置清单是否一致、有无多余或缺失。","answer":"A","chapter":"文档、配置与变更管理","difficulty":2,"explain":{"B":"物理配置审计查『东西齐不齐、版本对不对』,不直接验证功能是否符合需求。","C":"质量审计面向过程合规(是否按流程规范执行),与配置一致性无关。","D":"财务审计查资金账目,与配置无关。"},"id":"rk-zhishi-ch08-003","options":["功能配置审计","物理配置审计","质量审计","财务审计"],"source":"chapter","stem":"配置审计中,验证交付系统的『功能实现是否符合经批准的需求规格』,属于哪类审计?","subject":"综合知识","type":"single"},{"analysis":"保护期速记:发明 20 年、实用新型 10 年、外观设计 15 年(均自申请日起,示例口径)。","answer":"A","chapter":"法律法规与标准化","difficulty":1,"explain":{"B":"15 年是外观设计专利的保护期,不是实用新型。","C":"20 年是发明专利的保护期。","D":"50 年常见于著作权中发表权/财产权的保护口径,不属于专利权。"},"id":"rk-zhishi-ch09-001","options":["10 年","15 年","20 年","50 年"],"source":"chapter","stem":"我国现行专利制度中,实用新型专利权的保护期限是(自申请日起算,示例口径)?","subject":"综合知识","type":"single"},{"analysis":"招标公告/招标文件是要约邀请;投标人提交的投标文件是要约;招标人发出的中标通知书是承诺。","answer":"C","chapter":"法律法规与标准化","difficulty":2,"explain":{"A":"投标文件才是要约,招标公告只是邀请对方来投标。","B":"中标通知书才构成承诺。","D":"缔约过失与招标公告的性质判断无关。"},"id":"rk-zhishi-ch09-002","options":["要约","承诺","要约邀请","缔约过失责任"],"source":"chapter","stem":"从合同法(民法典合同编)角度理解,招标人发布的招标公告(招标文件)在法律上属于?","subject":"综合知识","type":"single"},{"analysis":"评标委员会由 5 人以上单数成员组成,其中技术、经济专家不少于总数的 2/3。","answer":"B","chapter":"法律法规与标准化","difficulty":2,"explain":{"A":"1/2 低于法定要求。","C":"3/4 无法律依据。","D":"委员会还须含招标人代表等,不需全部为技术经济专家。"},"id":"rk-zhishi-ch09-003","options":["1/2","2/3","3/4","全部"],"source":"chapter","stem":"依法组建的评标委员会中,技术、经济等方面的专家不得少于成员总数的(示例口径)?","subject":"综合知识","type":"single"},{"analysis":"IaaS 提供计算/存储/网络等基础设施;PaaS 在其上加平台;SaaS 直接交付应用。用户从 IaaS 到 SaaS 越来越省心。","answer":"A","chapter":"新一代信息技术与系统集成应用","difficulty":2,"explain":{"B":"开发与运行平台(含中间件)属于 PaaS。","C":"开箱即用的软件应用属于 SaaS。","D":"咨询服务不是云服务模式。"},"id":"rk-zhishi-ch10-001","options":["虚拟机、存储与网络等基础资源","应用开发与运行平台(含中间件)","可直接使用的在线办公软件","专业技术咨询服务"],"source":"chapter","stem":"下列资源中,属于 IaaS(基础设施即服务)向用户提供的是?","subject":"综合知识","type":"single"},{"analysis":"物联网标准三层:感知层(采集识别)、网络层(传输)、应用层(智能处理与服务)。","answer":"A","chapter":"新一代信息技术与系统集成应用","difficulty":1,"explain":{"B":"网络层负责把感知数据可靠地传输出去。","C":"应用层负责数据的智能处理与业务应用。","D":"『传输控制层』不是物联网标准三层之一。"},"id":"rk-zhishi-ch10-002","options":["感知层","网络层","应用层","传输控制层"],"source":"chapter","stem":"物联网体系架构中,负责通过传感器、RFID 等进行『识别与采集』的是哪一层?","subject":"综合知识","type":"single"},{"analysis":"区块链是通用的分布式可信账本技术,加密货币只是其典型应用之一,还可用于存证、溯源、数字身份、供应链金融等。","answer":"C","chapter":"新一代信息技术与系统集成应用","difficulty":2,"explain":{"A":"去中心化的分布式账本确实是区块链的核心特征。","B":"区块经哈希链式相连、改一处即全链失效,数据难以篡改。","D":"各节点通过共识机制对账本状态达成一致。"},"id":"rk-zhishi-ch10-003","options":["采用分布式账本,具有去中心化特征","区块经哈希链式连接,数据难以篡改","区块链只能用于加密货币","依靠共识机制使各节点账本保持一致"],"source":"chapter","stem":"关于区块链,下列说法错误的是?","subject":"综合知识","type":"single"},{"analysis":"大数据 4V=Volume(大量)、Velocity(高速)、Variety(多样)、Value(价值);真实性(Veracity)常作为扩展维度,标准 4V 中不含『准确』。","answer":"D","chapter":"新一代信息技术与系统集成应用","difficulty":1,"explain":{"A":"Volume(数据量大)是 4V 之一。","B":"Velocity(产生与处理速度快)是 4V 之一。","C":"Variety(来源类型多样)是 4V 之一。"},"id":"rk-zhishi-ch10-004","options":["数据量大(Volume)","处理高速(Velocity)","类型多样(Variety)","数据准确(Accuracy)"],"source":"chapter","stem":"下列选项中,不属于大数据『4V』典型特征的是?","subject":"综合知识","type":"single"},{"analysis":"私钥签名+公钥验证能确认『信息确实来自持有该私钥的发送方』且『内容未被改动』(真实性+完整性,防抵赖);它不提供保密,因为签名所用内容是公开可验的。","answer":"B","chapter":"信息安全与等级保护","difficulty":2,"explain":{"A":"保密性需用接收方公钥加密原文,签名机制本身不保密。","C":"可用性与签名的作用无关。","D":"密钥分发问题由证书体系(CA/PKI)解决,不是数字签名的作用。"},"id":"rk-zhishi-ch11-001","options":["消息的保密性","信息来源真实且内容未被篡改","消息传输的可用性","密钥分发的安全性"],"source":"chapter","stem":"发送方用自己的私钥对消息摘要加密(签名),接收方用发送方的公钥解密验证。该机制主要保证的是?","subject":"综合知识","type":"single"},{"analysis":"对称加密加解密共用一把密钥,速度快,但密钥分发困难;非对称加密使用公私钥对,解决了分发问题但速度慢,多用于签名与密钥交换。","answer":"B","chapter":"信息安全与等级保护","difficulty":1,"explain":{"A":"公钥/私钥成对是非对称加密的特征。","C":"数字签名通常用非对称(私钥签名、公钥验证)。","D":"密钥分发恰是对称加密要解决的难题。"},"id":"rk-zhishi-ch11-002","options":["使用公钥与私钥两把不同的密钥","加密和解密使用同一把密钥,速度快","主要用于数字签名","不存在密钥分发问题"],"source":"chapter","stem":"关于对称加密技术,下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"增量备份以『上一次备份』为基准,恢复时需全量备份+自该全量以来的全部增量(周一至周三)。","answer":"B","chapter":"信息安全与等级保护","difficulty":2,"explain":{"A":"增量备份自身不完整,缺少周日全量与周一、周二的增量。","C":"『全量+最后一次差异』是差异备份策略的恢复方式,与题干『每日增量』不符。","D":"仅全量只能恢复到上周日的状态,丢失周一至周三的变化。"},"id":"rk-zhishi-ch11-003","options":["仅周三当天的增量备份","周日全量+周一、周二、周三三次增量","周日全量+最后一次差异备份","仅最近一次全量备份"],"source":"chapter","stem":"备份策略为『每周日全量备份,其余每天增量备份』。周三上午系统故障需要恢复,通常需要哪几份备份才能完整恢复?","subject":"综合知识","type":"single"},{"analysis":"PMO 三类:支持型(当顾问、给模板)、控制型(要求遵守规范)、指令型(直接管理项目、控制力最强)。题干『直接管理、向其汇报』对应指令型。","answer":"C","chapter":"组织级项目管理与信息化监理","difficulty":2,"explain":{"A":"支持型只提供模板与咨询,不直接管理项目。","B":"控制型通过规范制度进行中度控制,通常不直接指挥项目。","D":"『顾问型』不是 PMO 的标准分类(标准为支持/控制/指令)。"},"id":"rk-zhishi-ch12-001","options":["支持型","控制型","指令型","顾问型"],"source":"chapter","stem":"某组织的办公室直接对项目进行管理,项目经理向其汇报。该机构最可能是哪种类型的 PMO?","subject":"综合知识","type":"single"},{"analysis":"CMMI 五级:1 初始(混乱)→2 已管理→3 已定义→4 量化管理→5 优化。","answer":"C","chapter":"组织级项目管理与信息化监理","difficulty":1,"explain":{"A":"第 2 级是已管理级。","B":"第 3 级是已定义级。","D":"第 5 级是优化级。"},"id":"rk-zhishi-ch12-002","options":["第 2 级","第 3 级","第 4 级","第 5 级"],"source":"chapter","stem":"CMMI 五级成熟度模型中,『量化管理级』是第几级?","subject":"综合知识","type":"single"},{"analysis":"三控=质量控制、进度控制、投资(成本)控制;两管=合同管理、信息管理;一协调=组织协调。合同管理属于『两管』。","answer":"D","chapter":"组织级项目管理与信息化监理","difficulty":2,"explain":{"A":"质量控制属于三控之一。","B":"进度控制属于三控之一。","C":"投资控制属于三控之一。"},"id":"rk-zhishi-ch12-003","options":["质量控制","进度控制","投资控制","合同管理"],"source":"chapter","stem":"信息系统工程监理的『三控、两管、一协调』中,下列不属于『三控』的是?","subject":"综合知识","type":"single"},{"analysis":"Earned value(EV)是挣值——『实际完成工作的计划价值』;『实际成本』的英文是 Actual cost(AC),两者不能混。","answer":"C","chapter":"专业英语与应试技巧","difficulty":1,"explain":{"A":"WBS(Work Breakdown Structure)即工作分解结构,对应正确。","B":"Critical path 即关键路径,对应正确。","D":"Stakeholder 即干系人,对应正确。"},"id":"rk-zhishi-ch16-001","options":["WBS —— 工作分解结构","Critical path —— 关键路径","Earned value —— 实际成本","Stakeholder —— 干系人"],"source":"chapter","stem":"下列英文术语与其中文含义对应错误的是?","subject":"综合知识","type":"single"},{"analysis":"项目管理十大知识领域中没有 Documentation management(文档管理);Risk、Stakeholder、Integration 均在其中。此题同时复习第 2 章十大领域,注意题干 NOT。","answer":"C","chapter":"专业英语与应试技巧","difficulty":2,"explain":{"A":"风险管理(Risk management)是十大领域之一。","B":"干系人管理(Stakeholder management)是第十大领域。","D":"整合管理(Integration management)是十大领域之一。"},"id":"rk-zhishi-ch16-002","options":["Risk management","Stakeholder management","Documentation management","Integration management"],"source":"chapter","stem":"Which of the following is NOT one of the ten knowledge areas of project management?","subject":"综合知识","type":"single"},{"analysis":"路由器工作在网络层、按 IP 地址选路;交换机工作在数据链路层、按 MAC 地址转发;集线器在物理层转发比特。","answer":"C","chapter":"网络与系统集成技术基础","difficulty":2,"explain":{"A":"路由器在网络层(IP 选路),不是数据链路层。","B":"交换机在数据链路层(MAC 转发),不是网络层。","D":"集线器工作在物理层,不是应用层。"},"id":"rk-zhishi-ch13-001","options":["路由器——数据链路层","交换机——网络层","路由器——网络层,负责按 IP 选路","集线器——应用层"],"source":"chapter","stem":"依据网络分层,下列『设备—工作层次』的对应中,正确的是?","subject":"综合知识","type":"single"},{"analysis":"UDP 无连接、速度快、允许少量丢包,适合实时性要求高的视频/语音;HTTP、FTP、SMTP 需要可靠传输,使用 TCP。","answer":"C","chapter":"网络与系统集成技术基础","difficulty":1,"explain":{"A":"网页浏览需要可靠传输,HTTP 基于 TCP。","B":"文件传输不容丢包,FTP 基于 TCP。","D":"邮件发送基于 TCP(SMTP)。"},"id":"rk-zhishi-ch13-002","options":["网页浏览(HTTP)","文件传输(FTP)","视频直播","邮件发送(SMTP)"],"source":"chapter","stem":"下列应用场景中,较适合使用 UDP 传输的是?","subject":"综合知识","type":"single"},{"analysis":"私有地址三大段:10.0.0.0/8、172.16.0.0/12(172.16~31.x.x)、192.168.0.0/16。172.16.3.5 命中私有段;其余为公网地址。","answer":"B","chapter":"网络与系统集成技术基础","difficulty":2,"explain":{"A":"8.8.8.8 是 Google 公共 DNS,属公网地址。","C":"202.108.22.5 属公网地址。","D":"223.5.5.5 是阿里公共 DNS,属公网地址。"},"id":"rk-zhishi-ch13-003","options":["8.8.8.8","172.16.3.5","202.108.22.5","223.5.5.5"],"source":"chapter","stem":"下列 IP 地址中,属于内网(私有)地址的是?","subject":"综合知识","type":"single"},{"analysis":"隔离性(Isolation):并发事务的执行互不影响;原子性=全做或全不做;一致性=事务前后数据满足约束;持久性=提交后修改不丢失。","answer":"C","chapter":"数据库与数据集成","difficulty":2,"explain":{"A":"原子性指事务要么全部成功要么全部回滚。","B":"一致性指事务前后数据保持一致与约束(如账目平衡)。","D":"持久性指提交后的修改永久保存、断电不丢。"},"id":"rk-zhishi-ch14-001","options":["原子性","一致性","隔离性","持久性"],"source":"chapter","stem":"事务 ACID 特性中,『并发事务之间互不干扰、彼此看不到对方未提交的数据』描述的是?","subject":"综合知识","type":"single"},{"analysis":"数据仓库四大特征:面向主题、集成、时变、非易失,服务于分析决策;『实时更新支撑在线交易』是事务型数据库(OLTP)的职责。","answer":"C","chapter":"数据库与数据集成","difficulty":2,"explain":{"A":"面向主题是数据仓库特征之一。","B":"集成清洗、统一口径是数据仓库特征。","D":"相对稳定、非易失(历史数据只读)是数据仓库特征。"},"id":"rk-zhishi-ch14-002","options":["面向主题组织数据","数据经过集成与清洗、口径一致","实时更新、直接支撑在线交易","数据相对稳定、非易失"],"source":"chapter","stem":"下列选项中,不属于数据仓库典型特征的是?","subject":"综合知识","type":"single"},{"analysis":"ETL=先抽取源数据,再转换(清洗、去重、统一口径),最后加载进数据仓库。","answer":"A","chapter":"数据库与数据集成","difficulty":1,"explain":{"B":"必须先抽取才能转换,顺序颠倒。","C":"转换在加载之前,不能先加载再转换。","D":"ETL 的第一步是抽取,加载不可能在最前。"},"id":"rk-zhishi-ch14-003","options":["抽取(Extract)→ 转换(Transform)→ 加载(Load)","转换 → 抽取 → 加载","抽取 → 加载 → 转换","加载 → 抽取 → 转换"],"source":"chapter","stem":"ETL 是数据进入数据仓库的核心过程,其正确执行顺序是?","subject":"综合知识","type":"single"},{"analysis":"白盒测试关注程序内部结构与路径(语句/分支/路径覆盖);黑盒只看需求与输入输出,不看内部。","answer":"B","chapter":"软件工程与测试基础","difficulty":1,"explain":{"A":"黑盒测试不阅读内部代码,只按需求测输入输出。","C":"验收测试由用户确认交付物是否符合预期。","D":"性能测试关注响应时间、吞吐量等指标。"},"id":"rk-zhishi-ch15-001","options":["黑盒测试","白盒测试","验收测试","性能测试"],"source":"chapter","stem":"测试人员阅读被测程序源代码、按内部逻辑设计路径覆盖用例,这种测试属于?","subject":"综合知识","type":"single"},{"analysis":"边界值分析要覆盖下边界两侧(0、1)与上边界两侧(100、101),再加一个正常值(如 50)。","answer":"A","chapter":"软件工程与测试基础","difficulty":2,"explain":{"B":"缺少下边界外 0 与上边界外 101 的越界验证点。","C":"全部在正常区间内,未测边界。","D":"未验证边界外侧(0 与 101)。"},"id":"rk-zhishi-ch15-002","options":["0、1、50、100、101","1、2、99、100","50、51","1、100"],"source":"chapter","stem":"某输入框要求填写 1~100 的整数。采用边界值分析设计测试数据,下列哪组数据最典型?","subject":"综合知识","type":"single"},{"analysis":"螺旋模型以风险驱动:每圈经历『计划→风险分析→开发→评审』,适合大型高风险项目;题干『每轮先做风险分析再决定是否继续』是其典型特征。","answer":"C","chapter":"软件工程与测试基础","difficulty":2,"explain":{"A":"瀑布模型顺序推进、怕变更,不以风险分析为阶段入口。","B":"原型模型为解决需求不清而快速建原型,重点不是风险。","D":"敏捷强调短迭代快速交付,但不以风险分析作为每轮的门槛。"},"id":"rk-zhishi-ch15-003","options":["瀑布模型","原型模型","螺旋模型","敏捷开发"],"source":"chapter","stem":"某大型项目技术风险较高、需求可能变化,管理者希望在每一轮都先做风险分析、再决定是否继续。最匹配的开发模型是?","subject":"综合知识","type":"single"},{"analysis":"找错题三段式:摘现象→指问题(对应管理原则/知识领域)→给纠正。先引用情景再判断,答案才有依据、可得分。","answer":"B","chapter":"案例·答题模板","difficulty":2,"explain":{"A":"只给结论没有依据和纠正,几乎不得分。","C":"不点明原做法错在哪,整改就失去对象。","D":"批评与题干无关的第三方属于答非所问。"},"id":"rk-case-ch01-001","options":["直接下结论「该做法错误」,不再展开","先摘录案例中的具体做法,再指出其违背的管理原则并给出纠正建议","只写整改方案,不评价原做法","通篇批评甲方或领导管理不善"],"source":"case","stem":"案例分析「找错题」中,最规范的作答第一步是?","subject":"案例分析","type":"single"},{"analysis":"接受范围外需求却未提交变更请求、做影响分析并经 CCB 审批,是典型的变更控制缺失导致的范围蔓延。","answer":"B","chapter":"案例·找错题通用","difficulty":2,"explain":{"A":"题干没有给出估算过程,不能臆断是估算方法问题。","C":"直接让开发实现并不必然说明技术不足。","D":"与考核机制无关。"},"id":"rk-case-ch02-001","options":["进度估算方法不正确","未执行变更控制流程(范围蔓延)","团队技术水平不足","缺少年终考核"],"source":"case","stem":"案例中「项目经理在客户口头提出新需求后直接安排开发实现」。该做法暴露的最核心管理问题是?","subject":"案例分析","type":"single"},{"analysis":"B 压缩 2 天后 A→B→D=11 天,但 A→C→D=12 天反超成为新的关键路径,故最短工期为 12 天(压缩后必须重算全图)。","answer":"B","chapter":"案例·网络图与进度","difficulty":3,"explain":{"A":"11 天忽略了压缩后 C 路径(12 天)成为新的关键路径。","C":"13 天是压缩前的工期,未体现压缩效果。","D":"10 天没有计算依据。"},"id":"rk-case-ch03-001","options":["11 天","12 天","13 天","10 天"],"source":"case","stem":"某网络计划中:A→B→D 路径总长 13 天(关键路径),A→C→D 路径 12 天。若将关键活动 B 压缩 2 天,项目最短工期变为?","subject":"案例分析","type":"single"},{"analysis":"CPI=EV/AC=90/110≈0.818;典型偏差 EAC=BAC/CPI=200/0.818≈244 万元。","answer":"C","chapter":"案例·挣值分析","difficulty":3,"explain":{"A":"220 是按非典型偏差公式 EAC=AC+(BAC−EV)=110+90 的另一种结果?错——AC+BAC−EV=110+200−90=220 正是非典型算法,题干要求按典型偏差继续。","B":"200 等于 BAC,隐含无偏差(CPI=1)的假设。","D":"250 对应 CPI=0.8 的口算结果,实际 CPI≈0.818。"},"id":"rk-case-ch04-001","options":["220","200","244","250"],"source":"case","stem":"某项目 BAC=200 万元,检查点 EV=90 万元、AC=110 万元。若按当前成本绩效(典型偏差)继续,完工估算 EAC 约为多少万元?","subject":"案例分析","type":"single"},{"analysis":"镀金=主动在范围外添加功能讨好客户;范围蔓延=客户不断加需求而项目组未加控制地接受。","answer":"B","chapter":"案例·范围与变更","difficulty":2,"explain":{"A":"蔓延是被动接受客户加需求,题干是开发主动多做。","C":"范围确认是验收核对,与主动加功能无关。","D":"与需求基线管理无关,且恰恰是未按基线执行。"},"id":"rk-case-ch05-001","options":["范围蔓延(scope creep)","镀金(gold plating)","范围确认","需求基线管理"],"source":"case","stem":"开发人员未与客户确认,主动为系统多做了一个客户没要求的演示功能以期获得好感。该现象属于?","subject":"案例分析","type":"single"},{"analysis":"单一来源依赖是典型威胁:应识别登记、评估(概率×影响),再规划应对(如备选供应商、存量预案、应急储备),并持续监控。","answer":"B","chapter":"案例·风险与干系人","difficulty":2,"explain":{"A":"直接终止合作属于过度反应,且替换供应商本身需要评估与过渡。","C":"只写周报没有应对动作,风险仍暴露。","D":"加班不能消除依赖风险,应对策略错配。"},"id":"rk-case-ch06-001","options":["立即终止与供应商的合作","将该风险记入风险登记册并规划备选/储备等应对","在周报中提一句即可","要求团队加班以规避风险"],"source":"case","stem":"项目核心组件仅依赖唯一供应商且未做任何备选评估。从风险管理角度,项目经理首先应当?","subject":"案例分析","type":"single"},{"analysis":"知识产权归属有约定从约定;题干已约定归乙方,故归乙方(示例口径,无约定时再依法定规则判断)。","answer":"B","chapter":"案例·采购合同法规","difficulty":2,"explain":{"A":"与合同明确约定冲突,约定优先。","C":"约定为归乙方而非共有。","D":"民事主体间的作品归属与国家无关。"},"id":"rk-case-ch07-001","options":["甲方(委托方)","乙方(开发方)","双方共有","国家"],"source":"case","stem":"委托开发合同中双方已明确约定「定制模块著作权归乙方」。依约定优先原则,该模块著作权应归?","subject":"案例分析","type":"single"},{"analysis":"十大知识领域:整合、范围、进度、成本、质量、资源、采购、沟通、风险、干系人管理——对应口诀「整范进成质 · 资采沟干风」。","answer":"C","chapter":"速记·项目管理口诀","difficulty":2,"explain":{"A":"文档管理不是独立知识领域(文档分散在各过程管理)。","B":"供应商相关活动归入采购管理,不存在独立领域。","D":"审计属于监控工具,不是独立知识领域。"},"id":"rk-suji-01-001","options":["文档管理","供应商绩效管理","干系人管理","安全审计管理"],"source":"suji","stem":"下列选项中,属于项目管理十大知识领域之一的是?","subject":"综合知识","type":"single"},{"analysis":"TF = LS − ES = 5 − 2 = 3 天(或 LF − EF = 9 − 6 = 3 天)。","answer":"B","chapter":"速记·计算公式","difficulty":3,"explain":{"A":"1 天是把 LS−EF(5−6 取绝对值)算错。","C":"4 天是 EF−ES(6−2),那是活动历时而非浮动。","D":"2 天无对应计算依据。"},"id":"rk-suji-02-001","options":["1","3","4","2"],"source":"suji","stem":"某活动最早开始 ES=2 天、最早完成 EF=6 天,最晚开始 LS=5 天、最晚完成 LF=9 天。该活动的总浮动时间 TF 为多少天?","subject":"综合知识","type":"single"},{"analysis":"私钥签名+公钥验证保证来源真实与内容完整(防抵赖);保密性要靠加密而非签名。","answer":"C","chapter":"速记·安全网络","difficulty":2,"explain":{"A":"签名不保密,保密需用接收方公钥加密。","B":"密钥分发恰是对称加密的难题。","D":"UDP 无连接、尽力而为,TCP 才可靠。"},"id":"rk-suji-03-001","options":["数字签名主要用于保证消息保密性","对称加密可彻底解决密钥分发问题","发送方用私钥签名、接收方用其公钥验证,可保证来源真实与内容完整","UDP 是面向连接的可靠传输协议"],"source":"suji","stem":"关于信息安全机制,下列说法正确的是?","subject":"综合知识","type":"single"},{"analysis":"保护期口诀:发明 20 年、实用新型 10 年、外观设计 15 年(示例口径,以现行法规为准)。","answer":"B","chapter":"速记·法规数字","difficulty":1,"explain":{"A":"10 年是实用新型的保护期。","C":"20 年是发明专利的保护期。","D":"50 年常见于著作权发表/财产权口径,不是专利。"},"id":"rk-suji-04-001","options":["10 年","15 年","20 年","50 年"],"source":"suji","stem":"我国现行专利制度中,外观设计专利权的保护期限是(自申请日起算,示例口径)?","subject":"综合知识","type":"single"},{"analysis":"预留时间/预算储备属于『接受』(主动接受:预留储备);转移是把后果转给第三方(保险、外包、担保)。","answer":"D","chapter":"速记·配置风险","difficulty":2,"explain":{"A":"买保险是把损失转给保险公司,属转移。","B":"用成熟技术降低风险概率/影响,属减轻。","C":"改变计划让风险不发生,属规避。"},"id":"rk-suji-05-001","options":["买保险——转移","改用成熟技术方案——减轻","取消高风险子活动并调整方案——规避","为高发风险预留缓冲时间——转移"],"source":"suji","stem":"下列「风险应对策略—做法」对应错误的是?","subject":"综合知识","type":"single"},{"analysis":"找错题三段式:摘现象→指问题(对应管理原则/知识领域)→给纠正;分条作答并多用术语(如『未执行变更控制』)。","answer":"B","chapter":"速记·案例话术","difficulty":2,"explain":{"A":"只有结论没有依据与纠正,几乎不得分。","C":"不点明问题,整改无对象,答非所问。","D":"通常要求指出多条,只答一条会漏分。"},"id":"rk-suji-06-001","options":["只写『管理太混乱』","每条按『现象+违背的管理原则+纠正建议』作答","只写一份长篇整改方案而不点明问题","只挑最严重的一条回答"],"source":"suji","stem":"案例分析要求『指出项目存在的问题』时,下列作答方式最规范、最易得分的是?","subject":"案例分析","type":"single"}],"cert":"ruanjian-kaoshi","chapters":[{"name":"信息化与系统集成技术","title":"第 1 章 · 信息化与系统集成技术","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch01-xinxihua/"},{"name":"案例·答题模板","title":"第 1 章 · 科目导学与答题模板","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch01-daoxue/"},{"name":"速记·项目管理口诀","title":"速记卡 1 · 项目管理口诀","url":"/ruanjian-kaoshi/books/suji-shouce/suji-01-xiangmu/"},{"name":"案例·找错题通用","title":"第 2 章 · 找错题高频点与话术","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch02-zhaocuo/"},{"name":"项目管理基础","title":"第 2 章 · 项目管理基础","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch02-xiangmuguanli/"},{"name":"速记·计算公式","title":"速记卡 2 · 计算公式","url":"/ruanjian-kaoshi/books/suji-shouce/suji-02-gongshi/"},{"name":"案例·网络图与进度","title":"第 3 章 · 网络图与进度案例套路","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch03-wangluotu/"},{"name":"范围与进度管理","title":"第 3 章 · 范围与进度管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch03-fanweijindu/"},{"name":"速记·安全网络","title":"速记卡 3 · 安全与网络","url":"/ruanjian-kaoshi/books/suji-shouce/suji-03-anquan/"},{"name":"成本与质量管理","title":"第 4 章 · 成本与质量管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch04-chengbenzhi/"},{"name":"案例·挣值分析","title":"第 4 章 · 挣值分析案例套路","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch04-zhengzhi/"},{"name":"速记·法规数字","title":"速记卡 4 · 法规与数字","url":"/ruanjian-kaoshi/books/suji-shouce/suji-04-falv/"},{"name":"案例·范围与变更","title":"第 5 章 · 范围与变更、配置管理案例套路","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch05-fanwei-biangeng/"},{"name":"风险与干系人管理","title":"第 5 章 · 风险与干系人管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch05-fengxian/"},{"name":"速记·配置风险","title":"速记卡 5 · 配置与风险","url":"/ruanjian-kaoshi/books/suji-shouce/suji-05-peizhi-fengxian/"},{"name":"资源与沟通管理","title":"第 6 章 · 资源与沟通管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch06-ziyuangoutong/"},{"name":"案例·风险与干系人","title":"第 6 章 · 风险与干系人案例套路","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch06-fengxian-ganxiren/"},{"name":"速记·案例话术","title":"速记卡 6 · 案例答题话术","url":"/ruanjian-kaoshi/books/suji-shouce/suji-06-huashu/"},{"name":"案例·采购合同法规","title":"第 7 章 · 采购、合同与法规案例套路","url":"/ruanjian-kaoshi/books/anli-fenxi/anli-ch07-caigou-hetong/"},{"name":"采购与合同管理","title":"第 7 章 · 采购与合同管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch07-caigouhetong/"},{"name":"文档、配置与变更管理","title":"第 8 章 · 文档、配置与变更管理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch08-wendangpeizhi/"},{"name":"法律法规与标准化","title":"第 9 章 · 法律法规与标准化","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch09-falvbiaozhun/"},{"name":"新一代信息技术与系统集成应用","title":"第 10 章 · 新一代信息技术与系统集成应用","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch10-xinyidai-xinxi/"},{"name":"信息安全与等级保护","title":"第 11 章 · 信息安全与等级保护","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch11-xinxianquan/"},{"name":"组织级项目管理与信息化监理","title":"第 12 章 · 组织级项目管理与信息化监理","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch12-zuzhiji-jianli/"},{"name":"网络与系统集成技术基础","title":"第 13 章 · 网络与系统集成技术基础","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch13-wangluo/"},{"name":"数据库与数据集成","title":"第 14 章 · 数据库与数据集成","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch14-shujuku/"},{"name":"软件工程与测试基础","title":"第 15 章 · 软件工程与测试基础","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch15-ruanjian/"},{"name":"专业英语与应试技巧","title":"第 16 章 · 专业英语与应试技巧","url":"/ruanjian-kaoshi/books/zonghe-zhishi/ch16-zhuanliyingyu/"}],"practiceUrl":"/ruanjian-kaoshi/practice/"}