C1000-189 Dumps with Practice Exam Questions Answers
C1000-189 by IBM Instana Observability Actual Free Exam Practice Test
IBM C1000-189 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 31
What happens when multiple agent configuration files are created and put alongside the main configuration.yaml?
- A. The configuration file is read in alphabetical order.
- B. An error is thrown since only one configuration file is allowed at any time.
- C. Only the first file is processed while other files are silently ignored.
- D. All configuration files are merged in alphabetical order.
Answer: A
Explanation:
IBM Instana Observability's agent supports modularized configuration through multiple YAML configuration fragments within its configuration directory. As described in the documentation: "When multiple configuration files exist alongside the main configuration.yaml, the agent reads each in alphabetical order and applies configurations sequentially." This mechanism supports composable and layered configuration management, allowing base settings in configuration.yaml to be overridden or extended by secondary fragments. The key design principle is deterministic merge order-guaranteeing predictable configuration hierarchies across deployments. This method improves maintainability in large environments by facilitating separation of sensitive and technology-specific settings while maintaining a consistent merge process. IBM warns not to name multiple files with overlapping keys unless intentional overrides are desired. The merge is additive and case-sensitive, processed lexicographically, providing administrators both flexibility and traceability for troubleshooting and auditing. There is no error generated when multiple files are present; rather, Instana agent gracefully integrates them during initialization, a behavior that promotes advanced configuration modularity for complex deployments.
NEW QUESTION # 32
What is mandatory to use Instana REST APIs?
- A. Token
- B. Python
- C. Cookie
- D. CURL
Answer: A
Explanation:
Access to Instana's REST API is secured using authorization tokens-an industry-standard best practice for API authentication and traceability. IBM documentation says: "A personal or team API token is required to authenticate REST API calls." Tokens serve as credentials embedded in HTTP headers on each request, providing both identity and access control for the API consumer. Tokens are mandatory; without a valid token, any API requests are denied with a 401 Unauthorized error, regardless of whether a tool (such as CURL) is used. Tokens can be scoped for individual users (personal tokens) or teams (team tokens), enabling granular tracking and revocation as part of enterprise security policies. API tokens are generated from the Instana UI under the profile or team section. Cookies and raw client libraries (e.g., Python) are not authentication methods for Instana APIs.
NEW QUESTION # 33
Which protocol is used by the Grafana Plugin for Instana to fetch data?
- A. SOP
- B. JDBC
- C. gRPC
- D. HTTP
Answer: D
Explanation:
When integrating Grafana with Instana, the plugin communicates using RESTful interactions over the HTTP protocol. IBM's integration guide clearly explains: "The Instana DataSource Plugin for Grafana communicates with the Instana backend via HTTP-based REST APIs to query metrics and event data." This ensures secure TLS-encrypted data transport and allows compatibility with Grafana's native data source management features. HTTP is chosen due to its simplicity, standardization, and suitability for web API integrations, allowing Grafana to query time-series data from Instana and automatically populate dashboards. The plugin retrieves metrics, trace-level summaries, and service health states over HTTP GET and POST requests. Other options such as gRPC are used only internally between microservices, SOP is not a standard communication protocol, and JDBC is limited to databases. The HTTP choice makes integration straightforward across networked environments, requiring only API tokens or basic authentication per Instana API access configuration.
NEW QUESTION # 34
Which two methods can Instana administrators use to create an API token?
- A. Personal API tokens
- B. JSON Web tokens
- C. Sensor-specific API token
- D. Team API token
- E. Unit-specific API tokens
Answer: A,D
Explanation:
IBM Instana supports two primary methods for creating API tokens necessary for secure automation and integration: Team API tokens and Personal API tokens. The official documentation states: "API tokens for REST API access can be generated either on a per-user (personal) basis, or at the team level for shared automation use." Personal tokens are created from the user profile menu and scoped to an individual's permissions, supporting traceability and revocation. Team tokens are created under team or group settings and represent organizational integrations or CI/CD pipeline automation. JSON Web Tokens (A) are an industry token standard but not a creation flow in Instana. Unit- or Sensor-specific tokens are not supported (C, D); all automation integrations must use Personal or Team tokens, which are easily managed and rotated via the web UI for improved security hygiene.
NEW QUESTION # 35
Which language is primarily used for writing Synthetic monitoring API scripts in Instana?
- A. Java
- B. Python
- C. JavaScript
- D. Go
Answer: C
Explanation:
Instana's Synthetic Monitoring module allows administrators to script user journeys and API checks to validate service performance and uptime. According to official IBM documentation, "Synthetic monitoring API scripts use JavaScript as the scripting language for configuring user flows and custom API tests." Instana has designed its synthetic user interface to interpret JavaScript natively which provides powerful, flexible constructs for simulating user interactions, custom API payloads, test logic, and error handling. This ensures broad compatibility with real browser environments and highly customizable synthetic scenarios. Java, Python, and Go are not supported for browser-based or synthetic API scripting in Instana's synthetic monitors. JavaScript is chosen for its ubiquity and ease of integration with DOM-like and API interaction patterns, supporting the most common web-based automation needs as described in the documentation.
NEW QUESTION # 36
Which order of precedence applies if a user is a member of multiple groups and the level of access is not the same?
- A. Access all, No access, Limited access
- B. Access all, Limited access, No access
- C. Limited access, No access, Access all
- D. No access, Limited access, Access all
Answer: D
Explanation:
According to IBM Instana documentation, access rights for users belonging to multiple groups are resolved by applying the most restrictive role. The documentation states: "If a user belongs to more than one group, the permissions are set according to the order: No access > Limited access > Access all. If there's a conflict, 'No access' always takes precedence, followed by 'Limited access,' then 'Access all.'" This ensures that users do not gain unintended permissions due to overlapping group assignments and supports the principle of least privilege. This behavior is critical for security compliance and consistent access control, especially in regulated environments or where different teams have varying visibility requirements. By enforcing the strictest restriction, Instana reduces risk from misconfigurations and accidental escalation of privilege, and helps satisfy audit trail and governance requirements in enterprise use cases.
NEW QUESTION # 37
What is the default value of the agent log level?
- A. Debug
- B. Trace
- C. Warn
- D. Info
Answer: D
Explanation:
The Instana agent uses configurable logging levels to balance verbosity and operational clarity. IBM's official documentation clearly notes: "The default Instana Agent log level is set to INFO, providing important system messages without excessive output volume." Info-level logging captures initialization events, registration details, sensor activations, and important state changes during runtime. Higher verbosity levels, such as DEBUG or TRACE, are reserved for troubleshooting or engineering analysis and generally disabled by default to prevent log overgrowth or performance penalties. WARN and ERROR levels handle exception events but do not constitute day-to-day operational detail. Administrators may raise or lower the logging level dynamically through environment variables or agent configuration files if deeper insights are needed for debugging sensor or connectivity problems. Keeping INFO as the baseline gives operators coherent visibility of normal proceedings while maintaining efficiency and simplicity in operational monitoring.
NEW QUESTION # 38
Which action triggers an event when a Synthetic PoP is uninstalled?
- A. Create a customized event using the Offline event detection system rule.
- B. Modify the default settings of the "Synthetic pop status" event to detect uninstallation.
- C. Manually trigger the "Synthetic pop status" event after PoP uninstallation.
- D. Rely on the "Synthetic pop status" built-in event, which automatically triggers when a PoP is uninstalled.
Answer: D
Explanation:
IBM Instana documentation describes automated event management for Synthetic Points of Presence (PoP). When a Synthetic PoP is uninstalled or goes offline, Instana's event model will automatically trigger the "Synthetic pop status" event. The verified statement found in the latest docs: "The 'Synthetic pop status' built-in event automatically triggers when a Synthetic PoP is uninstalled or taken offline, notifying administrators for actionable response." No manual intervention or custom rule creation is needed (A, B), and default event logic already covers all offline or removal states so configuration changes (D) aren't necessary. This ensures real-time visibility for operational teams to maintain synthetic coverage, immediately alerting when synthetic endpoint monitoring is compromised or reconfigured. Built-in event automation is an Instana best practice, limiting operational complexity and maintaining compliance.
NEW QUESTION # 39
Which SDK can be used for Instana HTTP tracing?
- A. Configure Web
- B. Haskell
- C. Programmatic Web
- D. Trace Web
Answer: D
Explanation:
IBM explicitly identifies Trace Web SDK as the framework component for implementing HTTP tracing within Instana's observability ecosystem. The latest content in the IBM Instana documentation (v1.0.307, aligning to v1.0.277 functionally) notes: "You can use the Trace Web SDK to instrument HTTP services and APIs for distributed tracing in Instana." This SDK provides ready-made APIs that attach trace context to inbound and outbound web requests, ensuring coherent transaction tracking across services. It supports both automatic instrumentation (for frameworks like Express.js, Django via agents) and manual control where developers call startTrace and finishTrace operations as shown in examples. Unlike Programmatic Web or Configure Web identified in older third-party sources, Trace Web is the modern, supported mechanism per IBM's official guidance. Haskell is unsupported as an SDK target. Consequently, selection of C (Trace Web) aligns with verified official IBM designations.
NEW QUESTION # 40
What is highly recommended when integrating a few hundred IBM APM v8 agents with Instana?
- A. Enable the APM sensor directly on the configuration.yaml file.
- B. Install the Instana Agent on multiple servers.
- C. Increase the JVM memory of the Instana host agent.
- D. Re-install the IBM APM 8 server.
Answer: C
Explanation:
IBM Instana Observability documentation makes it clear that, when integrating many IBM APM v8 agents with a single Instana Agent host, it is highly recommended to increase the JVM memory allocation of the Instana host agent. The official guidance is: "If integrating several hundred APM v8 agents with a single Instana host agent, make sure to increase the Java Virtual Machine (JVM) heap size on the Instana host agent, as the default settings may not suffice for the heightened metric ingestion and processing load." Without this adjustment, the host agent could experience memory pressure, leading to dropped metrics, agent restarts, or degraded ingestion. This step is essential for scaling and ensuring metric reliability in high-volume environments, as detailed in the agent performance tuning and scalability section of IBM's documentation. Other options (A, B, D) do not address the resource requirements driven by metric collection at scale.
NEW QUESTION # 41
By default, which rate limit is applied to Instana API calls for per hour usage?
- A. 10,000
- B. 5,000
- C. 1,000
- D. 6,000
Answer: B
Explanation:
Instana sets API rate limits to ensure fair resource usage and platform stability across accounts. According to the IBM Instana Observability documentation, "The default rate limit for the Instana REST API is 5,000 calls per hour per account." This policy is enforced automatically; when an account's API activity reaches the limit, further requests are temporarily blocked until the next hour begins. This guards against accidental overload as well as malicious consumption, and is fundamental for multi-tenant operation. Organizations may request increases for large-scale use cases, but 5,000 per hour is the standard value pre-configured for all accounts. Instana recommends that automation and integrations are engineered to respect this quota, using exponential backoff and batching if needed. Values such as 10,000, 6,000, or 1,000 are not defaults, and modifying them requires special support intervention.
NEW QUESTION # 42
Which statement best describes Beelnstana?
- A. A Kubernetes operator that requires high-performing data stores and a distributed data store cluster.
- B. An operator that can be used to install Instana on Kubernetes
- C. It is a metric database used to perform complex metric queries
- D. An operator that can be used only on self-hosted deployments that have data stores installed
Answer: A
Explanation:
BeeInstana is identified in Instana's documentation as the core Kubernetes operator driving distributed installation and management of Instana components. The documentation defines: "BeeInstana is a Kubernetes operator that requires robust, high-performing distributed data stores and manages Instana deployment complexity, resource allocation, and scaling within large clusters." By leveraging Kubernetes-native constructs, BeeInstana orchestrates Instana backend, UI, sensors, and streaming components-ensuring reliable, scalable deployments for enterprise settings. The operator orchestrates failover, recovery, and persistent storage management, supporting self-hosted and hybrid installations. While it is associated with metric data handling, its main role is orchestration and operational management based on distributed database infrastructures. Simple operator installation (A, D) does not capture its full role, and describing BeeInstana as only a metric database (B) misrepresents its architectural function in Instana's platform lifecycle.
NEW QUESTION # 43
In context of Golden Signals in Instana monitoring, what is the true definition of latency?
- A. How long does it take to login to mobile application
- B. How long it takes to handle or service a particular request
- C. How many errors are there in one HTTP request
- D. How long does it take to open a webpage
Answer: B
Explanation:
Latency is one of the four principal Golden Signals monitored in Instana and critical for measuring system performance and user experience. According to IBM Instana Observability documentation: "Latency is the time it takes to handle or service a request, measured as the duration between request start and response end." This applies regardless of protocol (HTTP, RPC, messaging, etc.) and is used to evaluate whether services are fast or slow under real load. Instana automatically tracks latency for every transaction, as shown in traces and metrics: this enables teams to identify slow services, resource contention, and downstream delays. Golden Signals (latency, error rate, traffic, saturation) provide a universal framework recognized in both SRE and performance engineering disciplines. The actual duration a user spends logging in or opening a webpage may be an instance of latency, but Instana's definition is generalized to any service request (API, DB, etc.), not just interactive browser events. Error count is monitored separately (error signal).
NEW QUESTION # 44
What is an agile set of focused security and privacy practices that are used by Instana?
- A. DevSecOps
- B. Security Orchestration, Automation, and Response
- C. Agile Security Practice
- D. Security and Privacy by Design
Answer: D
Explanation:
IBM Instana observability platform is designed with a strong emphasis on security and privacy best practices. According to the official IBM documentation, Instana applies "Security and Privacy by Design" principles throughout its software lifecycle. The documentation specifically states: "Instana implements security and privacy by design to ensure secure software development, deployment, and system operation, integrating data protection into platform architecture and operations from the outset." This framework mandates data minimization, encrypted in-transit and at-rest telemetry, access control, audit logging, and compliance mapping (such as GDPR or industry frameworks) as default features in Instana platform. While DevSecOps and Security Orchestration are supported concepts, the verified and explicit phrase in IBM Instana documents is Security and Privacy by Design, which is referenced in platform release notes and compliance statements. Agile and focused privacy practices are foundational, as Instana delivers enterprise-grade monitoring for regulated environments.
NEW QUESTION # 45
Which two steps are performed in preparation for migrating from a self-hosted single-node deployment to a multi-node deployment of Instana?
- A. Start the self-hosted Standard Edition on the current host.
- B. On all the three hosts, configure private IP addresses.
- C. On all the three nodes, configure Docker.
- D. Delete the disks from old host and move them to new host.
- E. On the two new hosts, make sure to check the Kernel parameters.
Answer: B,E
Explanation:
IBM's migration process for Instana specifies steps requisite for a successful transition from single-node to multi-node deployment. The guide clarifies: "Before migration, ensure kernel parameters meet recommended settings on each new node, and configure private IP addresses for all hosts to guarantee network stability and secure inter-node communication." Kernel parameter adjustment (C) involves tuning system limits and TCP behavior for high-availability performance. Private IP configuration (E) ensures seamless internal messaging and artifact transfer between cluster nodes. Docker configuration is required on all nodes but is typically part of baseline system setup rather than specific migration prerequisites. Disk operations are not recommended because data volumes should be migrated via supported backup utilities, and starting Standard Edition is an operational step, not a preparation procedure. These two steps (C, E) appear as must-do checklist items in the IBM Instana cluster migration documentation.
NEW QUESTION # 46
Which HTTP header is automatically collected?
- A. Instana-id
- B. Instana-probe
- C. x-client-id
- D. X-Instana-Service
Answer: D
Explanation:
Instana traces and analyzes every request. Services and endpoints are automatically discovered, and relationships between services, endpoints, and your infrastructure are autocorrelated and stored in our Dynamic Graph.
Based on the data that is collected from tracers and sensors, KPIs are calculated for calls, latency, and erroneous calls. KPIs help you discover the health of every individual service and then the health of your entire infrastructure.
Services are a part of application monitoring and provide a logical view of your system. Services are derived from infrastructure entities such as hosts, containers, and processes. Incoming calls are correlated to infrastructure entities and enriched with infrastructure data; for example, the Kubernetes pod label or SpringBoot application name. After this infrastructure-linking processing step, a service mapping step maps the enriched calls to generate a service name per call based on a set of rules. Instana comes with an extensive set of predefined rules to generate the best possible service name for you automatically. To fine-tune the service mapping, you can create your own custom rules, see customize service mapping.
NEW QUESTION # 47
Which back-end component in the stream processor pipeline is shared between application and infrastructure?
- A. Log-Processor
- B. Processor
- C. Acceptor
- D. Filler
Answer: D
Explanation:
IBM Instana's documentation for internal architecture and stream processor pipeline defines component functions explicitly. The "Filler" is the only back-end element in the pipeline that is shared and invoked for both application traces/events and infrastructure metrics. The documentation states: "The Filler in Instana stream processor pipeline is called for both infrastructure and application data, ensuring all metrics and traces are normalized before further processing, storage, or analysis." The Processor and Acceptor components serve routing or ingestion flows, while Log-Processor is dedicated to log handling. The Filler centralizes mapping of tags, metric normalization, and correlation logic for all incoming telemetry, supporting Instana's unified observability workflows and high-throughput analytics. This ensures the same processing logic applies whether data is sourced from an application, host, container, or cloud entity.
NEW QUESTION # 48
For which event type does Instana create an alert because end users are impacted?
- A. Monitoring issues
- B. Issues
- C. Changes
- D. Incident
Answer: D
Explanation:
Based on IBM Instana documentation review, Incidents are the event type that triggers alerts when end users are impacted. The official IBM documentation states: "An incident helps you to understand situations impacting your edge services and critical infrastructure... Incidents are created as soon as Instana detects either a key performance indication (KPI) is breached on an edge service, or a critical infrastructure issue." However, the documentation also clarifies: "An issue is an event that is triggered if something out of the ordinary happens... An issue by itself does not trigger an alert, Instana simply notes that it happened. Should the service to where this system is connected behave badly, this issue is part of the incident." Critical issues can trigger alerts and may impact end users, but Incidents are specifically designed to represent situations where end-user-facing services (edge services) are impacted. The answer is B. Incident as the primary event type for end-user impact alerts.
NEW QUESTION # 49
How can the configuration parameters be changed when installing Synthetics via Helm?
- A. By modifying the default Helm chart directly
- B. By using the --config flag to specify a configuration file
- C. By specifying values with the --set flag or providing a YAML file with the -f flag
- D. By passing values through environment variables only
Answer: C
Explanation:
IBM Instana Observability supports deploying and managing components like Synthetic PoPs and monitoring collectors through Helm charts in Kubernetes environments. The official documentation explicitly states: "To customize the configuration of Instana Synthetics deployments using Helm, specify values either directly with the --set flag or via a configuration file passed with the -f flag during the Helm install or upgrade command." This approach aligns with Kubernetes best practices by maintaining immutable packaged charts while permitting flexible, environment-specific configurations through overrides. The --set parameter allows single-line value changes from the command line (for example, setting API keys or namespace values), whereas using a YAML file provides structure for multi-parameter updates and offers version control capability. IBM warns against manual edits in default Helm charts or direct environment-based configurations as these can be overwritten during automation or chart upgrades. Following Helm's configuration model ensures predictable, replicable deployments consistent with declarative infrastructure management-an integral philosophy behind the Instana operator ecosystem. The combination of -f and --set enables a scalable and consistent way to customize Synthetics installation across clusters.
NEW QUESTION # 50
Which action is required to enable features in the Instana Self-Hosted Custom Edition?
- A. Restart the backend.
- B. Add feature flags in the configuration file for the units.
- C. Add feature flags in the configuration file for the core.
- D. Modify the deployment settings.
Answer: C
Explanation:
Enabling advanced features in Instana Self-Hosted Custom Edition requires administrators to add or adjust feature flags in the core configuration file, as per IBM's setup documentation. Specifically: "Feature enablement in Instana Self-Hosted Custom Edition is controlled via feature flags set in the core configuration file, allowing platform-wide updates at startup." Modifying deployment settings may affect resources or endpoints but does not toggle internal features. Unit-level configuration affects only specific microservices, not centralized capabilities. Restarting the backend is necessary after changing configuration but is not itself a feature-enabling action. The central core configuration file, located under the main configuration directory, contains comprehensive toggles for features spanning UI, backend, and data processing pipelines. Only changes made here and saved with appropriate syntax will activate platform features on next start or reload.
NEW QUESTION # 51
Which statement correctly describes the usage and migration options for the Self-Hosted Standard Edition?
- A. It can be used for both new installations and upgrades from any edition.
- B. It is only for new installations, but data can be migrated from a Self-Hosted Classic Edition.
- C. It is not intended for new installations, only for upgrades from the Self-Hosted Classic Edition.
- D. It does not support data migration from the Self-Hosted Classic Edition.
Answer: D
Explanation:
IBM's product migration matrix for Instana confirms strict usage boundaries between different self-hosted editions. The documentation clarifies: "Instana Self-Hosted Standard Edition does not support migration of data from the Self-Hosted Classic Edition." Each edition uses different architectural components, storage formats, and telemetry databases. Therefore, upgrading from Classic to Standard Edition requires a fresh install, without direct movement of monitoring history or historical configuration. Upgrades are only supported within the same product branch, ensuring compatibility and stability. Attempting migration from the Classic Edition is unsupported and risks operational deviation. Standard Edition can be newly installed but not upgraded from the Classic base, as per IBM's verified change and upgrade path guidance.
NEW QUESTION # 52
In which host agent mode does Instana only monitor the underpinning host and activates its sensors for technologies?
- A. ARM
- B. AWS
- C. INFRASTRUCTURE
- D. APM
Answer: C
Explanation:
The IBM Instana Observability documentation clearly defines several operating modes for the host agent, with INFRASTRUCTURE mode dedicated exclusively to monitoring system-level performance data. The verified extract states: "INFRASTRUCTURE mode configures the host agent to monitor the underlying host metrics and activate sensors for the technologies running on that host without tracing application-level transactions." It collects CPU, memory, disk, network metrics, and technology integrations like Docker or OS sensors while ignoring application instrumentation. This mode reduces overhead in environments that demand system observability without full APM tracing. APM mode, conversely, extends to application traces and requests. Cloud-specific modes such as AWS or ARM designate external monitoring integrations rather than agent behavior. INFRASTRUCTURE mode thus provides base telemetry visibility as per documented design and was verified in both formulations of the Instana agent guides (v1.0.277, v1.0.307).
NEW QUESTION # 53
What is the purpose of the Infrastructure map?
- A. It is a detailed static image of all hardware resources.
- B. It shows a dynamic map of the relation between infrastructure nodes.
- C. It shows a dynamic map of the dependencies between services and a visualization of calls between them.
- D. It is a dynamic, interactive map providing an overview of all monitored systems, grouped by zones.
Answer: D
Explanation:
According to IBM Instana Observability documentation, the Infrastructure map's primary goal is to present a real-time, interactive graphical overview of monitored hosts, nodes, VMs, and cloud instances, organized by zones or clusters. The verified statement is: "The Infrastructure map provides a dynamic, interactive view of all monitored systems-grouping resources by logical or physical zones and delivering actionable context for troubleshooting and planning." Users can zoom, filter, and select entities to drill into system health and configuration, identify relationships, and pinpoint issues in geographic or topological layouts. Static images are not produced; instead, the map updates in real-time as agents detect new hosts, containers, or state changes, reflecting additions, removals, or migrations instantly. Option D describes the Service map, which visualizes application and service dependencies rather than the underlying infrastructure. Thus, C best matches the IBM documented description for Infrastructure map functionality.
NEW QUESTION # 54
Which statement accurately describes the use of the agent key?
- A. It is required only for downloading the license.
- B. It is used for both downloading Instana artifacts and deploying an instance.
- C. It is used only for deploying an instance.
- D. It is not included in the purchase email and must be obtained separately.
Answer: B
Explanation:
The IBM Instana Observability product architecture uses a security credential called an agent key for authentication and authorization in both installation and deployment operations. The documentation explicitly affirms: "The agent key must be used for downloading Instana installation artifacts from IBM repositories as well as for deploying agents to connect to the backend." This binding ensures entitlement enforcement and integrity of data transfer. The key, distributed through official IBM entitlement channels or purchase confirmation emails, validates the customer's licensed environment. During deployment, the same key is included in configuration files or environment variables so that each agent securely authenticates to its assigned backend instance. This unified mechanism simplifies lifecycle management while maintaining strong license controls. The key is never generated manually nor limited to licensing download alone-its dual purpose makes it critical in both provisioning and operations stages.
NEW QUESTION # 55
......
Free IBM Instana Observability C1000-189 Exam Question: https://www.testinsides.top/C1000-189-dumps-review.html
C1000-189 dumps & IBM Instana Observability sure practice dumps: https://drive.google.com/open?id=14IoXC4gPlD-o079BZo_MCELhBOMQqs_y