CCBA日本語のPDF試験材料2025年最新の実際に出るCCBA日本語問題集
更新されたのはIIBA CCBA日本語問題集PDFオンラインエンジン
質問 # 248
レガシー システムのサポートを担当するビジネス アナリスト (BA) は、システムの使いやすさを評価するために顧客調査を作成しました。調査を配布する前に、BA は何をすべきでしょうか。
- A. プロジェクトスポンサーとリスクレジスターを確認する
- B. 調査を含めるようにプロジェクト計画を更新する
- C. プロジェクトスポンサーと調査を検証する
- D. 顧客とシステムのやりとりを観察する
正解：D
解説：
The business analyst (BA) should observe customer interaction with the system before distributing the survey to assess its usability. According to the BABOK Guide, observation is "a technique used to elicit information by viewing and understanding activities and their context" 4. By observing the customer interaction with the system, the BA can gain insights into the actual usage, behavior, problems, and preferences of the customers, which can help the BA design a more effective and relevant survey. Validating the survey with the project sponsor, reviewing the risk register with the project sponsor, and updating the project plan to include the survey are important steps, but they should be done after observing the customer interaction with the system. Reference: 4: BABOK Guide, Version 3, Section 10.24 Observation
質問 # 249
プロジェクトで変更要求が一般的に増加するのはいつですか?
- A. プロジェクトの立ち上げ中。
- B. プロジェクトの開始に向けて。
- C. プロジェクト スコープ管理プロセス中。
- D. プロジェクトの終わりに向かって。
正解：B
解説：
According to the PMBOK Guide, change requests are more likely to occur in the early phases of a project, when the project scope is not well defined and the uncertainty is high. As the project progresses, the scope becomes clearer and the changes are more controlled. Therefore, option A is the best answer.
Option B is incorrect because the project scope management processes are not a specific time period in the project, but rather a set of activities that can occur throughout the project. Option C is incorrect because the project's launch is not a phase of the project, but rather a milestone that marks the start of the project execution. Option D is incorrect because change requests tend to decrease towards the end of the project, when the project is close to completion and the scope is well established.
質問 # 250
Tracy は組織のビジネス アナリストであり、ソリューション スコープに必要な要件を収集して特定しました。要件の管理を開始する前に、Tracy は何をする必要がありますか? 最適な回答を選択してください。
- A. Tracy は WBS 内の要件を分解する必要があります。
- B. Tracy は、要件を完全に管理するために、要件の役割、責任、および所有者を特定する必要があります。
- C. Tracy は、利害関係者に要件を伝え、同意と承認を得る必要があります。
- D. Tracy は、まずメリットを管理するために、各要件の費用対効果分析を作成する必要があります。
正解：B
解説：
Before managing the requirements, Tracy must identify the roles, responsibilities, and owners of the requirements, as this is one of the tasks under the business analysis planning and monitoring knowledge area1.
This task involves defining who will be involved in the requirements development and management process, what their roles and responsibilities are, and who has the authority to approve or change the requirements. This helps to ensure clarity, accountability, and collaboration among the stakeholders and the business analyst. The other options are not prerequisites for managing the requirements, but rather activities that may be performed during or after the requirements analysis and design definition knowledge area2. Decomposing the requirements in WBS (A) is a technique for breaking down the requirements into smaller and more manageable components. Creating cost-benefits analysis of each requirement (B) is a technique for evaluating the value and feasibility of the requirements. Communicating the requirements to the stakeholders for their consent and approval (D) is a task for verifying and validating the requirements. References: CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS, Business Analysis Expert Certification, CCBA® | IIBA®
質問 # 251
次のどれが、ビジネスアナリストが要件検証タスクで使用する一般的な手法ではありませんか?
- A. 問題追跡
- B. 受け入れおよび評価基準の定義
- C. 費用便益分析
- D. 構造化されたウォークスルー
正解：C
解説：
Cost-benefits analysis is a technique used in the business case development task, not in the requirements verification task. The other options are all general techniques that can be used to verify the requirements with the stakeholders and ensure they are complete, correct, and consistent. References: BABOK® Guide, section
4.5.3, page 117; section 4.6.3, page 123.
質問 # 252
ビジネス アナリスト (BA) は、先週の大半を、今後のプロジェクトの新規、削除、および変更されたコンポーネントのカタログ作成に費やしました。BA がこの作業を行う主な目的は何ですか。
- A. ドメインの専門家を特定する
- B. 現在の状態を文書化する
- C. 主要業績評価指標を確立する
- D. 将来の状態を定義する
正解：D
解説：
According to the BABOK Guide, defining the future state is a technique for strategy analysis. This technique can help the BA perform the work of cataloguing the new, removed, and modified components of an upcoming project, as it describes how the organization or business unit will operate after implementing a change3. By doing so, the BA can identify the gaps between the current state and the future state, and define the solution scope and approach. Therefore, the correct answer is B. Reference: BABOK Guide, [CCBA Mock Test]
質問 # 253
ビジネス アナリスト (BA) は、新しいシステムの要件を文書化し、承認のために要件を準備しています。要件が完全に理解され、追跡可能であることを保証するために役立つのは次のどれですか。
- A. 要件は適切に分類されています
- B. 要件は規制基準を満たしている
- C. 要件が検証されている
- D. 要件はレビューのために抽出されます
正解：A
解説：
This is because classifying requirements helps to ensure that they are fully understood and traceable by grouping them into categories based on their type, source, priority, or other criteria. Classifying requirements also helps to avoid duplication, ambiguity, and inconsistency among the requirements. Extracting requirements for review (A) is not a valid option, as it implies that the requirements are already documented and ready for approval. Validating requirements © is a good practice, but it does not ensure traceability, which is the ability to link the requirements to the business needs, solution components, and test cases. Meeting regulatory standards (D) is a quality criterion, but it does not ensure that the requirements are fully understood and traceable. References: CCBA Practice Test, CCBA Mock Test
質問 # 254
必要なリソースが整理され、引き出しに利用できるようにするために最もよく説明される引き出し活動はどれですか?
- A. 誘導結果の確認
- B. 利害関係者の要件の管理
- C. 引き出しの準備
- D. 引き出しの計画
正解：C
解説：
Preparing for elicitation is the elicitation activity that ensures that the needed resources are organized and available for the elicitation. It involves understanding the scope of the elicitation activity, selecting appropriate techniques, and planning for or procuring appropriate supporting materials and resources1. Preparing for elicitation helps to define the desired outcomes of each elicitation activity, and ensures that the stakeholders have the information they need to provide and understand the nature of the activities they will participate in2.
The other options are not correct because:
Confirming elicitation results is the elicitation activity that ensures that the information obtained from the elicitation is accurate, complete, clear, and consistent3.
Planning for elicitation is the business analysis planning and monitoring activity that defines the approach and activities for eliciting, analyzing, and managing requirements4.
Managing stakeholder requirements is the requirements lifecycle management activity that ensures that the requirements and designs are aligned with the needs of the stakeholders and the solution scope5.
References:
Conducting elicitation activity - The Functional BA, section "Guide elicitation activity" Prepare for Elicitation, section "Description of Change" Confirm Elicitation Results, section "Description of Change" Plan Business Analysis Elicitation, section "Description of Change" Manage Stakeholder Requirements, section "Description of Change"
質問 # 255
次のすべては、組織の準備状況を評価するタスクへの入力ですが、どれを除きますか?
- A. エンタープライズアーキテクチャ
- B. 利害関係者の懸念
- C. リスクレジスター
- D. ソリューションの範囲
正解：C
解説：
According to the BABOK Guide, the task of assessing organizational readiness involves analyzing the readiness, willingness, and ability of the stakeholders and the organization to accept, adopt, and use the solution1. This task requires inputs from various sources that provide information on the current and desired state of the organization, the solution scope and objectives, the stakeholder roles and responsibilities, and the potential impacts and risks of the change. Among the inputs listed in the question, the one that is not an input to the task of assessing organizational readiness is risk register. A risk register is an output of the task of identifying risks, which involves identifying and documenting the uncertainties that may affect the business analysis work or the solution2. A risk register is not an input to the task of assessing organizational readiness, but rather an input to the task of managing risks, which involves planning and implementing responses to the identified risks2.
The other options are all correct inputs to the task of assessing organizational readiness:
Enterprise architecture: Enterprise architecture is a description of the current and future structure and behavior of an organization's processes, information systems, personnel, and organizational sub-units3. It provides an input to the task of assessing organizational readiness, as it helps to understand the alignment, dependencies, and gaps between the current and future state of the organization and the solution1.
Solution scope: Solution scope is a description of the boundaries of the solution, including what is in and out of scope, the key assumptions and constraints, and the major features and functions3. It provides an input to the task of assessing organizational readiness, as it helps to define the scope and objectives of the change, and the expected benefits and outcomes of the solution1.
Stakeholder concern: Stakeholder concern is a statement of a need, expectation, problem, or opportunity that is relevant to one or more stakeholders3. It provides an input to the task of assessing organizational readiness, as it helps to identify and analyze the stakeholder needs, expectations, interests, and attitudes towards the change, and the potential impacts and issues that may arise from the solution1. Reference:
1: BABOK Guide, section 6.2 Assess Organizational Readiness, page 116
2: BABOK Guide, section 4.7 Identify Risks, page 126; section 4.8 Manage Risks, page 130
3: BABOK Guide, section 3.8 Glossary, page 516-524
質問 # 256
最近の調査によると、新しく実装されたシステムには、ユーザーが使用したことのない機能があることがわかりました。調査レポートを確認した後、最高経営責任者 (CEO) は、ビジネス価値を提供しない機能の今後の実装は避ける必要があると強調しました。ビジネス アナリスト (BA) は、将来の要件がビジネス ニーズを満たすようにするために何をする必要がありますか?
- A. 要件をトレースする際にビジネスとの関連性を考慮する
- B. テストシナリオがビジネス要件に適合していることを確認する
- C. 要件を伝えるために適切な形式を選択する
- D. ユーザーとのフォーカスグループを実施してフィードバックを得る
正解：A
解説：
The business analyst should consider the business relevance of the requirements while tracing them to the business needs, goals, and objectives. This will help the BA to ensure that the requirements are aligned with the business value and provide a clear rationale for their inclusion in the solution scope. By tracing the requirements, the BA can also identify and eliminate any unnecessary or redundant features that do not contribute to the business value.
References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Life Cycle Management knowledge area, where tracing requirements is a key task for the BA12. It also relates to the Business Analysis Planning and Monitoring knowledge area, where the BA should define the business analysis approach and the requirements prioritization process
質問 # 257
ビジネス アナリスト (BA) が要件パッケージを準備し、関係者に提示する準備が整いました。パッケージを提示する目的は何ですか?
- A. プロジェクトの進捗状況を確認する
- B. 情報の共通理解を確保するため
- C. プロジェクトの完了を文書化する
- D. 分析アプローチを定義する
正解：B
解説：
The scenario describes a task that involves presenting a requirements package to the stakeholders. The requirements package is a document that contains the requirements and related information for the project and the solution. The purpose of presenting the package is to ensure a shared understanding of the information among the stakeholders, which is essential for achieving stakeholder alignment, agreement, and commitment.
Presenting the package also provides an opportunity for the BA to elicit feedback, validate requirements, and resolve any issues or conflicts.
References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the communicate business analysis information task as part of the solution evaluation knowledge area12. The CCBA® resources also describe the types and formats of documents that can be used to communicate business analysis information, such as requirements packages1
質問 # 258
組織の強みと弱みを同業他社や競合他社と比較する調査として最もよく説明される誘導手法は何ですか?
- A. 比較分析
- B. ブレインストーミング
- C. ベンチマーク
- D. 市場分析
正解：C
解説：
Benchmarking is an elicitation technique that is best described as a study to compare the strengths and weaknesses of an organization against its peers and competitors. Benchmarking involves measuring and evaluating the performance, processes, or practices of an organization or a system with those of other organizations or systems that are considered to be the best in the industry or the domain. Benchmarking helps to identify the gaps, opportunities, and best practices for improvement and innovation. Benchmarking can be done at various levels, such as strategic, operational, functional, or technical. The other options are not elicitation techniques that can achieve the same goal as benchmarking. Brainstorming is a technique for generating a large number of ideas or options for solutions in a creative and collaborative way. Market analysis is a technique for researching and analyzing the market trends, demands, and preferences of the customers or the users. Comparativeanalysis is a technique for comparing and contrasting the similarities and differences between two or more items, such as concepts, theories, models, etc. Reference:
Top 10 Most Common Requirements Elicitation Techniques
What elicitation technique is best described as a study to compare the strengths and weaknesses of an organization against its peers and competitors?
Types of Elicitation Techniques for the Business Analyst
質問 # 259
要件抽出ワークショップを数回開催した後、ビジネス アナリスト (BA) は、2 人のビジネス関係者がどの議論でも発言しなかったことに気付きました。次のワークショップで BA は何をすべきでしょうか。
- A. 2 人のビジネス関係者が準備ができたら発言すると想定して、通常どおり進めます。
- B. 他の利害関係者が彼らの意見を聞けるように、2 人の利害関係者だけに発言を許可します。
- C. 2 人の関係者は関与していないと思われるため、次回の会議から除外します。
- D. 出席者全員に意見を求め、各関係者が発言して意見を述べる時間を確保します。
正解：D
解説：
Comprehensive and Detailed Ensuring active participationby all stakeholders is crucial forcomplete and accurate requirements elicitation. The BA shouldfacilitate the workshop in a way that encourages input from quieter stakeholders.
BABOK Guide (Chapter 3.2 - Conduct Elicitation)emphasizes the need foractive stakeholder engagement to gather comprehensive requirements.
Allowing only the two stakeholders to speak (Option A)may create bias or resentment.
Omitting them from the next meeting (Option C)ignores potential valuable insights.
Assuming they will speak when ready (Option D)risks missing critical feedback.
質問 # 260
ビジネス アナリストとして、引き出し活動の結果を記録して文書化するのに適した方法を認識する必要があります。次のどれが、引き出しを文書化する有効な方法とは見なされませんか。
- A. ボイスメール
- B. イベントの結果を説明する文書
- C. ホワイトボード
- D. 音声録音
正解：A
解説：
Voice mails are not a valid method for documenting elicitation because they are not reliable, consistent, or traceable. Voice mails can be easily deleted, distorted, or misunderstood. They do not provide a clear record of the elicitation results, nor do they allow for verification, validation, or feedback from the stakeholders. The other methods, such as whiteboards, audio recordings, and written documentation, are valid methods for documenting elicitation because they can capture the information, insights, and agreements from the elicitation activities in a more structured, accessible, and transparent way12. References:
1: BABOK® Guide, Version 3.0, p. 39
2: Business Analysis Elicitation and Collaboration (IIBA -ECBA)
質問 # 261
ビジネス アナリスト (BA) は、特定されたプロセス全体でデータをどのように、誰が使用するかを判断するのに適した手法を調査しています。BA はどの手法を選択する必要がありますか?
- A. データ辞書
- B. ステークホルダー リスト、マップ、またはペルソナ
- C. 意思決定モデル
- D. CRUD (作成、ロード、更新、削除) マトリックス
正解：D
解説：
The BA should select CRUD (Create, Read, Update, and Delete) matrix as the technique that would be appropriate for determining how and who uses data across the identified processes. CRUD matrix is a table that shows the actions that different roles or stakeholders can perform on data entities or objects within a system or solution. CRUD matrix can help to define the data access rights and permissions for each role or stakeholder, as well as the data dependencies and interactions among processes.
The other options are incorrect because:
Option A is incorrect because stakeholder list, map, or personas are not techniques for determining how and who uses data, but techniques for identifying and analyzing stakeholders. Stakeholder list, map, or personas are tools that provide information about the characteristics, needs, expectations, and influences of stakeholders. Stakeholders are individuals or groups who have an interest or stake in a change or solution.
Option B is incorrect because data dictionary is not a technique for determining how and who uses data, but a technique for defining and describing data. Data dictionary is a repository that contains the definitions, attributes, formats, and relationships of data elements or objects within a system or solution.
Data dictionary can help to standardize and document the data requirements and specifications for a solution.
Option D is incorrect because decision model is not a technique for determining how and who uses data, but a technique for modeling and analyzing decisions. Decision model is a graphical representation of the logic, rules, criteria, and outcomes of decisions within a system or solution. Decision model can help to simplify and clarify the decision-making process and its impact on the solution.
References:
BABOK Guide v3, section 10.16: CRUD Matrix
CCBA Practice Test, question 5
質問 # 262
どのステークホルダー マップが、ステークホルダーをソリューションに近づけたり遠ざけたりすることで、ステークホルダーの相対的な影響、インパクト、関係性を示していますか?
- A. トルネード図
- B. RACIマトリックス
- C. タマネギ図
- D. 管理図
正解：C
解説：
An onion diagram is a type of stakeholder map that shows the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution. An onion diagram consists of concentric circles that represent different layers of stakeholder involvement and interest in the solution. The innermost circle contains the core team members who are directly responsible for the solution. The next circle contains the key stakeholders who have high influence and impact on the solution. The outer circles contain the secondary and tertiary stakeholders who have lower influence and impact on the solution, but still need to be considered and communicated with12.
The other options are not correct because:
A RACI matrix is a type of stakeholder map that shows the roles and responsibilities of stakeholders by assigning them to one of four categories: Responsible, Accountable, Consulted, or Informed. A RACI matrix does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution3.
A control chart is a type of statistical tool that shows the variation in a process over time and helps to identify the causes of variation. A control chart is not a type of stakeholder map and does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution4.
A tornado diagram is a type of sensitivity analysis tool that shows the effect of changing the value of one input variable on the output variable. A tornado diagram is not a type of stakeholder map and does not show the relative influence, impact, and relation of stakeholders by plotting them closer to or farther away from the solution5.
References:
Onion Diagram, section "Description of Change"
Stakeholder Mapping 101: A Quick Guide to Stakeholder Maps - ProjectManager, section "Onion Diagram" RACI Matrix, section "Description of Change" Control Chart, section "Description of Change" Tornado Diagram, section "Description of Change"
質問 # 263
ビジネス アナリスト (BA) は、新しいプロジェクトについて、主要な主題専門家 (SME) といくつかの引き出しワークショップを設定しました。すべての SME はワークショップの招待を受け入れましたが、法務 SME は招待に応答しませんでした。最初のワークショップは来週に予定されており、BA は法務 SME に電話で連絡を取ろうとしましたが、失敗しました。BA はどのように進めればよいでしょうか。
- A. 法務SMEデスクに立ち寄って、プロジェクトにおける彼または彼女の関与と意見の重要性について情報に基づいた話し合いをしましょう。
- B. 最初のワークショップを進め、回答がなかったことをプロジェクトの問題として捉え、プロジェクトマネージャーが対処する
- C. 法務SMEマネージャーにメールで未回答をエスカレーションし、法務SMEが出席するよう依頼する
- D. 法務SMEのスケジュールを再確認し、公開カレンダーの空き状況に基づいてすべてのワークショップを再調整します。
正解：B
解説：
Elicitation workshops are a technique that involves bringing together a group of stakeholders to elicit, analyze, and validate requirements for a project. Elicitation workshops require careful planning, preparation, and facilitation to ensure that the objectives are met and the outcomes are documented. Elicitation workshops also depend on the participation and collaboration of the relevant stakeholders, especially the subject matter experts who have the knowledge and expertise on the project domain.
If the business analyst has set up a number of elicitation workshops with key subject matter experts on a new project, and one of them has not responded to any invitations, the business analyst should proceed with the first workshop and capture the non-response as a project issue for the project manager to address. This is the best course of action because it allows the business analyst to continue with the planned elicitation activities and avoid delays or disruptions to the project schedule. It also ensures that the non-response is communicated and escalated to the appropriate authority, who can take the necessary actions to resolve the issue and ensure the involvement and input of the legal SME in the future workshops.
References: BABOK Guide v3, page 54; CCBA Mock Test, question 6
質問 # 264
マトリックス ドキュメント アプローチを使用して要件を指定およびモデル化するには、要件のどのような条件を満たす必要がありますか?
- A. 要件は均一な構造を持つ必要があります。
- B. 要件には共通の特性が必要です。
- C. 要件には、時間、コスト、品質などの評価された目標が必要です。
- D. 要件には相反する値が必要です。
正解：A
解説：
The matrix documentation approach is used to specify and model requirements that are complex but uniform in structure. This means that the requirements can be broken down into simple elements that can be inputted into a matrix. A matrix is a rectangular array of numbers, symbols, or expressions, arranged in rows and columns. Matrices can be used to represent various types of requirements, such as data dictionaries, gap analysis, requirements traceability, and business rules analysis. Matrices can help to communicate information to a specific audience, confirm information, identify information gaps, and prevent the duplication of information. References:
Specifying and modeling requirements - The Functional BA
Selecting Requirements Documentation Techniques for Software Projects: a Survey Study
質問 # 265
ビジネス ユーザーと要件仕様をウォークスルーした後、グループは、新しい政府規制により 5 つの要件が必須になったと判断しました。会議後、ビジネス アナリスト (BA) は何をすべきでしょうか。
- A. 決定をプロジェクトマネージャーにエスカレートし、すべてのユーザーに再度確認する
- B. システムアナリストがユーザーにデモするための要件のプロトタイプを作成するのを支援する
- C. 要件の優先順位を更新し、その理由を記録する
- D. テストアナリストに、テストケースが新しい要件のみをカバーするように作成されていることを確認するよう依頼します。
正解：C
解説：
According to the BABOK® Guide, a business analyst (BA) should manage and maintain the requirements throughout the business analysis process. This includes prioritizing the requirements based on their relative value, risk, difficulty of implementation, and stakeholder preferences. A BA should also document the rationale for the prioritization and communicate any changes to the relevant stakeholders. In this scenario, the BA should update the priority of the five requirements that are now mandatory due to new government regulations, and record the reason for doing so. This way, the BA can ensure that the requirements reflect the current business needs and comply with the external constraints. The BA can also inform the project team and other affected stakeholders about the changes and their implications for the project scope, schedule, budget, and quality. References:
[BABOK® Guide], section 4.5: Manage Requirements
CCBA Exam Questions & Answers with Explanations, question 416
質問 # 266
ビジネス アナリスト (BA) がソフトウェア ソリューションの要件を検証しています。BA は、重要と判断された項目が最終的な要件成果物に含まれていることを確認する必要があります。次のどれが BA がこのタスクを完了するのに役立ちますか?
- A. 優先順位
- B. 要件マトリックス
- C. チェックリスト
- D. 評価基準
正解：C
解説：
The scenario describes a task that involves verifying requirements for a software solution. The verification process is a part of the requirements life cycle management knowledge area, which is one of the six knowledge areas covered by the CCBA® certification. According to the CCBA® Handbook and the IIBA® website, checklists are one of the techniques that can be used to verify requirements, as they provide a structured way of ensuring that all important items are included and accounted for in the final requirements deliverable12. Checklists can also help to identify any gaps, inconsistencies, or errors in the requirements12.
References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the requirements life cycle management knowledge area, including the task of verify requirements12. The CCBA® resources also describe the techniques and tools that can be used to perform each task in the business analysis process12.
質問 # 267
ビジネス アナリストとして、引き出し活動の結果を記録して文書化するのに適した方法を認識する必要があります。次のどれが、引き出しを文書化する有効な方法とは見なされませんか。
- A. ボイスメール
- B. イベントの結果を説明する文書
- C. ホワイトボード
- D. 音声録音
正解：A
解説：
Voice mails are not a valid method for documenting elicitation because they are not reliable, consistent, or traceable. Voice mails can be easily deleted, distorted, or misunderstood. They do not provide a clear record of the elicitation results, nor do they allow for verification, validation, or feedback from the stakeholders. The other methods, such as whiteboards, audio recordings, and written documentation, are valid methods for documenting elicitation because they can capture the information, insights, and agreements from the elicitation activities in a more structured, accessible, and transparent way12. Reference:
1: BABOK Guide, Version 3.0, p. 39
2: Business Analysis Elicitation and Collaboration (IIBA -ECBA)
質問 # 268
有名なスーパーマーケット チェーンを復活させるために、新しい最高経営責任者 (CEO) が任命されました。CEO はオンライン ショッピングを導入して売上を伸ばしたいと考えています。ほとんどの店舗は人員が不足しており、メンテナンスが課題となっています。次のどれが資産と見なされますか。
- A. 銀行融資の金利上昇
- B. オンラインショッピングサイト
- C. 店舗維持費
- D. ブランドの評判
正解：D
解説：
Comprehensive and Detailed Brand reputationis a strategicassetthatprovides competitive advantage, influences customer perception, and contributes to business growth.
BABOK Guide (Chapter 6.1 - Define Solution Approach)states thatbusiness assets include brand value, customer loyalty, and intellectual property.
Online shopping website (Option A)is a potential asset but is not yet implemented.
Interest on loans (Option B) and maintenance expenses (Option D)are financial liabilities, not assets.
質問 # 269
......
IIBA CCBA日本語問題集PDFのベストを目指すなら問題集を使おう！高得点目指すならここ：https://jp.fast2test.com/CCBA-JPN-premium-file.html