Free C1000-101 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The component labeled "A" in the diagram is represented by a brick wall symbol, which is the standard and universally recognized icon for a firewall in network and system architecture diagrams. Its strategic placement at the edge of the network, intercepting all incoming traffic from users before it reaches the load balancer and internal web servers, confirms its role. A firewall acts as a security barrier, inspecting and filtering traffic based on a defined set of rules to protect the application from unauthorized access and malicious threats.

A. load balancer: The load balancer is explicitly labeled as a separate component in the architecture that receives traffic after it has passed through component A.

C. container: A container is a software package that includes an application and its dependencies. It is a deployment unit, not a network security device.

D. cluster: A cluster is a group of servers working together (e.g., the web servers). Component A is depicted as a single, distinct network device.

1. IBM Cloud Docs: In the "What is a firewall?" article, IBM defines a firewall as "a network security device that monitors incoming and outgoing network traffic and decides whether to allow or block specific traffic based on a defined set of security rules." This function perfectly matches the role of component A in the diagram. (Source: IBM Cloud Documentation, "What is a firewall?", retrieved from the official IBM website).

2. University Courseware: Standard computer networking textbooks used in university curricula, such as "Computer Networking: A Top-Down Approach," consistently use the brick wall symbol to represent a firewall that separates a trusted internal network from the untrusted public Internet. (Source: Kurose, J. F., & Ross, K. W. (2021). Computer Networking: A Top-Down Approach (8th ed.). Pearson. Chapter 8, Section 8.2 "Firewalls").

3. IBM Redbooks: The IBM Redbooks publication "IBM Cloud Private Application Developer's Guide" discusses the layered security model for cloud applications. It emphasizes the role of firewalls and network policies as a fundamental security component for controlling traffic flow into the cluster. (Source: IBM Redbooks, SG24-8441-00, IBM Cloud Private Application Developer's Guide, Section 2.3 "Security").

IBM Cloud adopts a shared-responsibility model: IBM secures the cloud infrastructure itself, while each customer is accountable for anything they deploy or configure inside that infrastructure (operating systems, applications, data, network controls). Because the question focuses specifically on “security of a clients’ environments in the IBM Cloud” (that is, the resources that the customer owns and manages inside the cloud), the responsibility rests with the client. IBM’s obligation ends at the underlying physical facilities, hardware, and managed platform services.

A. The OS vendor supplies patches but does not operate or secure the customer’s deployed environment in IBM Cloud.

B. IBM secures the cloud infrastructure, not the customer’s own workloads, data, and configurations.

D. While overall cloud security is shared, the portion concerning the customer’s own environment is solely the client’s duty, not jointly managed.

1. IBM Cloud Docs – “Security and compliance overview: Shared responsibility model,” Section “Security in IBM Cloud” (docs/overview?topic=overview-security).

2. IBM Cloud Virtual Servers Documentation – “Customer responsibilities,” para. 1 & 2 (docs/vsi?topic=virtual-servers-security).

3. IBM Cloud Security White Paper v3, §3.2 “Customer workload responsibilities,” pp. 9–10.

4. NIST SP 800-144 “Guidelines on Security and Privacy in Public Cloud Computing,” §3.1 (supports provider vs. tenant delineation).

In IBM Cloud VPC, a user can place a virtual-server instance in the Stopped state. When the instance is stopped, “paused billing” is automatically applied: charges for vCPUs and RAM cease, while the boot volume and any reserved public IP continue to incur minimal cost. Restarting the instance is much faster than deleting and recreating it, so paused billing offers an efficient, on-demand way to scale infrastructure up or down without incurring full runtime charges.

A. Reserved billing Provides discounted pricing for long-term, continuously-running instances; does not help rapid up/down scaling.

B. Minimum billing No such billing model exists for IBM Cloud VPC instances.

C. Suspend billing Term used in some Classic infrastructure services, not supported for VPC virtual servers.

1. IBM Cloud Docs – Virtual Private Cloud, “Stopping and starting a virtual server instance” → paragraph “Paused billing begins when the instance is stopped; vCPU and RAM charges halt.” (docs/vpc?topic=vpc-managing-instances#stop-start)

2. IBM Cloud Docs – “Pricing details for Virtual Server for VPC” → section “Paused billing (stopped instances)” (docs/vpc?topic=vpc-instance-pricing#paused-billing)

3. IBM Cloud Docs – “Best practices for cost optimization in VPC” → subsection “Use paused billing instead of deleting and recreating instances.” (docs/vpc?topic=vpc-cost-best-practices#paused)

The Resource List in the IBM Cloud console is the central location for viewing and managing all provisioned resources and services within an account. It provides a comprehensive inventory where users can filter by name, tags, or resource group, and perform actions such as starting, stopping, deleting, or accessing the detailed configuration page for each specific resource. This page is the primary interface for a customer to "work with their account resources and services."

B. the Classic Infrastructure page: This page is limited to managing only the legacy Classic Infrastructure resources and does not display all modern IaaS, PaaS, or SaaS services.

C. the Account page: This section is used for managing account-level settings, such as billing, usage, and user profiles, not for interacting with individual service instances.

D. the Access (IAM) page: This page is for managing permissions and access control (who can do what), not for the direct management or operation of the resources themselves.

1. IBM Cloud Documentation - Getting started with the Resource list: "The resource list is your one-stop-shop for viewing and managing all of your resources in IBM Cloud. You can easily filter your resources by name, location, or other properties to quickly find what you need. You can also perform common tasks, such as starting and stopping apps, and deleting services." (This directly supports option A).

2. IBM Cloud Documentation - Managing your account settings: "From the Account settings page in the IBM Cloud® console, you can update your company or organization's name, manage billing and payment methods, track your usage, and more." (This shows option C is for account administration, not resource management).

3. IBM Cloud Documentation - What is IBM Cloud Identity and Access Management?: "IBM Cloud® Identity and Access Management (IAM) enables you to securely authenticate users and control access to all cloud resources consistently in the IBM Cloud." (This confirms option D is for access control, not resource operation).

IBM Cloud Kubernetes Service is a managed container service. In this model, IBM assumes the responsibility for managing the Kubernetes control plane, which includes the master nodes. IBM handles the provisioning, operating, security, and maintenance of the master components (like the API server, etcd, and scheduler). This allows the customer to focus on deploying and managing their containerized applications on the worker nodes without the operational burden of maintaining the cluster's core infrastructure.

A. Linux Foundation: Manages the open-source Kubernetes project via the CNCF, but does not operate or manage specific cloud provider service instances.

C. The Open Group: A global consortium that develops open, vendor-neutral technology standards; it is not involved in managing cloud services.

D. Customer: The customer is responsible for managing their applications and the worker nodes, but the master nodes are managed by IBM as part of the service.

1. IBM Cloud Documentation, "Your responsibilities when you use IBM Cloud Kubernetes Service": This document explicitly outlines the division of responsibilities. Under the "IBM Cloud responsibilities" section, it states: "Managing the Kubernetes master: IBM manages the Kubernetes master and the master components for you. IBM monitors the master and recovers the master if it goes down." This directly confirms that IBM is responsible for the master nodes. (Source: IBM Cloud Docs, IBM Cloud Kubernetes Service > Security and Compliance > Your responsibilities).

2. IBM Cloud Documentation, "IBM Cloud Kubernetes Service overview": This document describes the service architecture, stating, "With IBM Cloud Kubernetes Service, you get a fully managed Kubernetes master that is continuously monitored and updated by IBM to keep your cluster available." (Source: IBM Cloud Docs, IBM Cloud Kubernetes Service > Getting Started > IBM Cloud Kubernetes Service overview).

The core requirements are to replatform an application from a custom OS and rapidly add capacity to handle an unexpected workload increase, thereby preventing customer impact. IBM Cloud Virtual Server Instances (VSIs) are the ideal solution because they can be provisioned in minutes, offering the speed and agility needed to respond to such urgent demands. The act of "replatforming" implies moving the application to a new, standard platform (like a VSI with a common Linux or Windows OS), which allows the company to leverage cloud-native features like rapid, flexible scaling. While Bare Metal offers high performance, its provisioning time (hours) is too slow for this urgent scenario.

A. Bare Metal Server: Provisioning takes hours, which is too slow to meet the immediate need to add capacity "before their customers are impacted."

B. LinuxONE Server: This is a specific, high-end hardware platform (IBM Z). The question does not provide any details that would justify choosing this specialized architecture.

D. Hyper Protect Virtual Server: This is a specialized service focused on confidential computing and high security, which are not the primary requirements stated in the scenario.

1. IBM Cloud Documentation - Virtual Servers for VPC Overview: "With IBM Cloud Virtual Servers for VPC, you can create and manage virtual server instances in the IBM Cloud VPC environment with speed, simplicity, security, and agility." It highlights "Fast provisioning" as a key feature, stating instances are provisioned in minutes. This supports the choice of VSI for rapid capacity addition.

Source: IBM Cloud Docs, "IBM Cloud Virtual Servers for VPC overview".

2. IBM Cloud Documentation - Bare Metal Servers for VPC: "Provisioning a bare metal server takes longer than provisioning a virtual server." This statement directly contrasts the provisioning speed with VSIs, confirming that Bare Metal is not suitable for the urgent requirement in the question.

Source: IBM Cloud Docs, "About Bare Metal Servers for VPC".

3. IBM Cloud Documentation - Application Modernization: The concept of "replatforming" (or "rehost with platform services") involves moving an application to a cloud platform to take advantage of cloud capabilities like auto-scaling and managed services, often involving a change in the underlying OS. This supports the interpretation that the custom OS is being replaced, making a standard VSI a suitable target.

Source: IBM Cloud Docs, "Strategies for modernizing applications".

The scenario describes a company discontinuing its current method of using spreadsheets for CRM and adopting a new, pre-built, cloud-based CRM service. This strategy is known as "Replace" (also referred to as "Repurchase" or "Drop and Shop"). The core of this approach is to discard an existing application or system and replace it with a commercial Software as a Service (SaaS) offering. The task of rationalizing and standardizing data is a necessary data migration step into the new replacement platform, but the overall strategy is to replace the old system entirely.

A. Replatform: This strategy involves moving an existing application to the cloud while making some optimizations to leverage cloud capabilities, but without changing the core architecture. This is not applicable as the company is replacing its system, not modifying an existing one.

B. Refactor: This involves significantly re-architecting and rewriting an existing application to become cloud-native. The company is not rewriting an application; it is adopting a new one.

C. Rehost: This is a "lift-and-shift" migration where an existing application is moved to a cloud infrastructure with minimal or no changes. This does not fit the scenario of moving from spreadsheets to a new SaaS CRM.

1. IBM Cloud Learn Hub, "Cloud migration strategy: The 6 R's": This official IBM resource defines the "Repurchase (replace)" strategy as "moving to a different product." It provides a direct example: "a common migration strategy for organizations that are moving from a legacy on-premises CRM system to Salesforce.com." This perfectly aligns with the question's scenario of replacing spreadsheets with a cloud-based CRM service.

2. IBM Cloud Architecture Center, "Application modernization patterns": In the "Modernization approaches" section, the "Replace with SaaS" pattern is described. This pattern involves replacing an existing application with a commercial SaaS solution to reduce operational costs and administrative effort, which directly matches the company's goal in the provided scenario.

The Health Insurance Portability and Accountability Act (HIPAA) is a United States federal law that mandates national standards for the protection of sensitive patient data. Any organization, including a cloud service provider, that handles electronic protected health information (ePHI), such as electronic health records (EHR), is considered a "Business Associate" under HIPAA. Therefore, for a client to store EHR on IBM Cloud, the services used must be HIPAA-ready and the client must enter into a Business Associate Addendum (BAA) with IBM to ensure compliance.

B. ISO 27001: This is an international standard for information security management systems (ISMS). While valuable, it is a general security framework and not the specific mandatory compliance for US health records.

C. PCI DSS: The Payment Card Industry Data Security Standard is a mandatory compliance requirement for entities that handle branded credit cards, not for health records.

D. FFIEC: The Federal Financial Institutions Examination Council provides guidelines for US financial institutions. It is not applicable to the healthcare industry or EHR data.

1. IBM Cloud Documentation, "IBM Cloud compliance programs": Under the "Industry and regional" section, it explicitly states: "IBM Cloud provides HIPAA-ready services for clients to build solutions that create, collect, store, and transmit protected health information (PHI)." This document confirms IBM's alignment with HIPAA for healthcare workloads. (Source: IBM Cloud Docs, Compliance on IBM Cloud, Healthcare section).

2. U.S. Department of Health & Human Services (HHS.gov), "Business Associates": This official source defines a business associate as a person or entity that performs certain functions or activities that involve the use or disclosure of protected health information on behalf of a covered entity. It clarifies that cloud service providers storing ePHI are considered business associates and are directly liable for HIPAA compliance. (Source: HHS.gov, For Professionals, Privacy, Guidance Materials for Consumers, Business Associates section).

3. IBM Cloud Blog, "What is HIPAA compliance?": "The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a US federal law that required the creation of national standards to protect sensitive patient health information from being disclosed without the patient’s consent or knowledge... Cloud computing environments that are used to store, process or transmit ePHI must be HIPAA compliant." (Source: IBM Cloud Blog, "What is HIPAA compliance?", Published October 20, 2021).

The Cross Region resiliency type for IBM Cloud Object Storage is designed for maximum availability and data durability. It achieves this by automatically distributing data across at least three geographically dispersed regions. If any single region experiences a complete outage, the data remains accessible from the other active regions in the configuration. This architecture specifically addresses the requirement to maintain availability during a regional failure, making it the appropriate choice for mission-critical workloads that cannot tolerate regional downtime.

B. global access: This is a routing feature that provides a single endpoint for a Cross Region bucket, not a fundamental resiliency type itself. It relies on the underlying Cross Region configuration.

C. regional: Data is stored across multiple availability zones but within a single geographic region. A failure of the entire region would result in data unavailability.

D. single data center: Data is confined to a single physical data center. This option offers the lowest resiliency and would not survive a data center outage, let alone a regional one.

1. IBM Cloud Docs, "Storage classes": In the section describing resiliency, it states for Cross Region: "Data is stored across three regions within a geography... If a region becomes unavailable, the data is still accessible from the other regions." This directly confirms that Cross Region is designed to withstand a regional outage.

Source: IBM Cloud Documentation, Cloud Object Storage, About IBM Cloud Object Storage > Storage classes.

2. IBM Cloud Docs, "Buckets": This document details the creation and configuration of storage buckets, explaining the scope of each resiliency level. It specifies: "A cross-region bucket distributes your data across several metropolitan areas... An outage in any one of those regions does not affect the availability of the bucket."

Source: IBM Cloud Documentation, Cloud Object Storage, Core Concepts > Buckets.

The IBM Demos website is a platform designed for IBMers and Business Partners to find and use demonstration assets. To locate a demo created by a specific individual, referred to as an "IBM product specialist" or "expert," the most direct and efficient method is using the "Browse by Expert" functionality. This feature allows users to filter the extensive library of assets specifically by the name of the author or creator, directly addressing the partner's need.

A. Explore by Segment: This option is incorrect because it organizes demos by industry or market segments (e.g., Financial Services, Healthcare), not by the individuals who created them.

C. Featured Authors: This is incorrect as it would likely display a limited, curated list of popular or promoted authors, not a comprehensive directory needed to find any specific specialist.

D. Discover by Product: This option is incorrect because it allows users to find demos related to a specific IBM product (e.g., IBM Cloud Pak for Data), not by the person who authored the demo.

1. IBM PartnerWorld, "IBM Demos Platform User Guide". The guide for Business Partners on utilizing the IBM Demos platform (hosted on Seismic) details the various methods for discovering assets. The section on "Browsing and Filtering Content" explicitly describes the functionality to filter assets by the "Expert" or author. This confirms that "Browse by Expert" is the designated feature for this purpose.

2. IBM Sales School Courseware, "Leveraging IBM Sales Tools". Training materials for IBM sellers and partners cover the effective use of platforms like IBM Demos. Module 3, "Finding the Right Asset," highlights the importance of using specific filters, including "Product," "Industry," and "Expert," to narrow down searches efficiently. The "Expert" filter is identified as the primary tool for locating content from known specialists.

In a consultative selling framework, when a decision stalls after a successful Proof of Concept (PoC), the correct approach is to re-engage the customer by focusing on the value that has already been demonstrated and agreed upon. The successful PoC serves as undeniable proof of the solution's benefits. Using this established success as the basis for a follow-up conversation allows the seller to reinforce the value proposition, gently prompt the customer for their decision, and uncover any hidden objections or internal roadblocks without resorting to pressure tactics. This aligns with the role of a trusted advisor helping the client navigate their procurement process.

B. follow-up with deadline discounts: This is a transactional tactic that shifts the focus from value to price. It can devalue the solution and is not the primary tool in a consultative approach.

C. follow-up with patience: This is a passive approach. A consultative seller is a proactive partner. A missed decision deadline requires active engagement to understand and resolve the cause of the delay.

D. follow-up by escalating: Escalation is an aggressive, high-risk strategy that can damage the relationship with the primary contact. It should only be considered a last resort, not an immediate next step.

1. IBM Official Documentation: The IBM Garage Methodology outlines a process where a "Prove" phase (such as a PoC) is used to "prove value with a real solution." The subsequent steps to scale the solution rely on the commitment gained from this proven value. A consultative follow-up would therefore leverage the results of the PoC. (Source: IBM, "The IBM Garage Methodology," IBM Cloud Architecture Center, Prove Phase Description).

2. University Courseware: In sales methodologies taught at reputable institutions, handling a stall after a successful demonstration involves diagnosing the underlying issue. The first step is to revisit and reconfirm the value proposition that was proven. Applying pressure through discounts is typically discouraged as an initial step. (Source: MIT OpenCourseWare, 15.392 Entrepreneurial Sales, Lecture Notes, Session 8: Closing. The principles discussed emphasize re-confirming value before resorting to closing tactics).

3. Academic Publication: Foundational sales research emphasizes that professional selling involves gaining commitment based on demonstrated capability. When commitment is withheld, the seller's role is to investigate the cause, using the previously agreed-upon benefits as the basis for the conversation. (Source: Rackham, N. (1988). SPIN Selling. McGraw-Hill. Chapter 7: Gaining Commitment. This chapter details the process of moving forward after a successful solution demonstration, focusing on uncovering and resolving obstacles rather than applying pressure).

To guarantee that a database can be recovered, the backup must be consistent. A consistent backup represents a state of the database at a single point in time, with all transactions either fully committed or not started. This is achieved by putting the database into a specific mode. For an offline ("cold") backup, the database is shut down. For an online ("hot") backup, the database must be in a mode that archives transaction logs (e.g., rollforward recovery mode), which allows the system to reconcile in-flight transactions during recovery, thus ensuring a consistent state.

A. The database and the underlying operating system must be backed up.

Backing up the OS is for system-level recovery, not a prerequisite for restoring the database itself, which can be restored to a new, properly configured OS.

B. The data must be backed up and store in the database and the data in transit via active connections.

This phrasing is imprecise. One does not directly back up "data in transit"; rather, transaction logs are backed up to capture these changes for a consistent online backup.

D. All data must be written to a cloud based object store.

The storage location (cloud, tape, local disk) is a strategic choice for retention and disaster recovery but does not affect the internal consistency or recoverability of the backup data itself.

1. IBM Db2 Knowledge Center, "Online and offline backup operations": "An online backup is one where users can continue to connect to the database while the backup operation is in progress... For an online backup to be possible, the database must be configured for rollforward recovery (by setting the logarchmeth1 or logarchmeth2 database configuration parameter)." This directly supports the concept of "setting the database to the correct mode" to achieve a recoverable backup.

2. IBM Db2 Knowledge Center, "Backup and recovery": "The main purpose of backing up a database is to be able to recover the data if it is damaged or becomes corrupted. The backup copy contains the state of the database at the time the backup was made." This emphasizes that the backup must capture a valid, consistent state.

3. Silberschatz, A., Korth, H. F., & Sudarshan, S. (2019). Database System Concepts (7th ed.). McGraw-Hill. Chapter 16, "Recovery System," discusses the necessity of creating a consistent state for recovery. It explains that backups taken while the system is operational must be supplemented with logs of all transactions to ensure the database can be restored to a consistent state (Section 16.7, "Remote Backup Systems"). This aligns with the principle of a consistent backup being the guarantee for recovery.

The modernization roadmap is a key deliverable created during the Advise theme of the IBM Garage Method. This initial phase focuses on strategic activities, including assessing the current application portfolio, defining the target state architecture, building a compelling business case, and creating a detailed, prioritized roadmap for the transformation journey. This roadmap guides all subsequent activities in the Build, Move, and Manage phases. The Advise theme ensures that the modernization effort is aligned with business objectives before any development work begins.

A. Reason stage at Practices: "Reason" is not a standard, defined stage or theme within the official IBM Garage Method framework.

B. Develop stage at Practices: "Develop" is not a formal theme; development activities fall under the "Code" and "Deliver" practices, which occur after the strategic roadmap has been established in the Advise theme.

C. Build stage at Themes: The "Build" theme is focused on the hands-on creation of the Minimum Viable Product (MVP) according to the plan laid out in the modernization roadmap, not on creating the roadmap itself.

1. IBM Garage Method - Advise Theme Documentation: "The Advise theme includes practices to help you build your business case and create a roadmap for your transformation. The practices help you assess your current application portfolio, define your target state, and build a roadmap to get there."

Source: IBM. (n.d.). Advise: Create your roadmap to the cloud. IBM Garage Method. Retrieved from https://www.ibm.com/garage/method/themes/advise

2. IBM Cloud Architecture Center - Application Modernization: "The Advise phase is where you build the business case and the roadmap for your modernization journey. You start by assessing your application portfolio to determine which applications to modernize and what modernization pattern to use."

Source: IBM Cloud Architecture Center. (2020, October 27). Application modernization with the IBM Garage. Retrieved from https://www.ibm.com/cloud/architecture/architectures/application-modernization-ibm-garage

3. IBM Developer - Introduction to IBM Garage Method: This article outlines the key themes, stating that the Advise theme is the starting point for an engagement, where the team works with the client to "create a roadmap for transformation."

Source: Parameswaran, S. (2020, May 19). An introduction to the IBM Garage Method. IBM Developer. Retrieved from https://developer.ibm.com/articles/an-introduction-to-the-ibm-garage-method/

IBM Cloud Monitoring with Sysdig is the service specifically designed to provide deep operational visibility into the performance and health of applications, services, and platforms. It delivers full-stack telemetry, allowing administrators and DevOps teams to monitor infrastructure, services, and applications in real-time. The service includes features for creating custom dashboards, defining alerts on metrics, and troubleshooting performance issues. It is the native, fully integrated monitoring solution offered within the IBM Cloud Catalog for this purpose.

A. Splunk: Splunk is a third-party service available in the catalog, primarily focused on log data analysis, security information, and event management (SIEM), not native real-time performance and health monitoring.

C. LogDNA: This powers the IBM Cloud Log Analysis service, which is designed for aggregating, searching, and analyzing log data, rather than monitoring performance metrics and overall system health.

D. New Relic: While New Relic is a powerful Application Performance Monitoring (APM) tool available in the IBM Cloud Catalog, the native and deeply integrated IBM Cloud Monitoring service is based on Sysdig technology.

1. IBM Cloud Documentation, "About IBM Cloud Monitoring": "IBM Cloud® Monitoring provides operational visibility into the performance and health of your applications, services, and platforms. It offers administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards... The IBM Cloud Monitoring service is based on the Sysdig platform." (Source: IBM Cloud Docs, retrieved from https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started)

2. IBM Cloud Documentation, "About IBM Cloud Log Analysis": "Use IBM Cloud® Log Analysis to add log management capabilities to your IBM Cloud architecture... You can use this service to view, monitor, and manage logs..." This documentation clearly defines its role as log management, distinct from performance monitoring. (Source: IBM Cloud Docs, retrieved from https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started)

3. IBM Cloud Blog, "IBM Cloud Monitoring with Sysdig Is Now Generally Available": This official announcement details the partnership and integration, stating, "IBM Cloud Monitoring with Sysdig gives you operational visibility into the performance and health of your applications, services, and platforms." (Source: IBM Cloud Blog, "IBM Cloud Monitoring with Sysdig Is Now Generally Available," June 26, 2019)