EC-Council 312-50V9 Exam Prep
Certified Ethical Hacker Exam V9 (Page 3 )

• SQL injection: Manipulates database queries through application input.
• XML external entities (XXE): Abuses XML parsers to access files, internal systems, or other resources.
• Cross-Site Request Forgery (CSRF): Tricks an already authenticated user’s browser into sending an unwanted request. It generally does not steal session cookies.

• Products ? OrderHistory: Products is 1, OrderHistory is many (1:*)

• Date ? OrderHistory: Date is 1, OrderHistory is many (1:*)

• Undefined or blank values
• Relationship matching problems
• Duplicate or conflicting keys
• Errors when querying the model

• Normalize all values to upper- or lowercase in the source query or Power Query.
• Add an index or surrogate key when values that differ only by case must remain distinct.

• Vulnerability scanner: Finds known technical weaknesses in systems or applications, but does not provide complete supply-chain visibility.
• Penetration test: Simulates attacks against defined targets; it is narrower than a full supply-chain analysis.
• SCAP: A set of standards and protocols for automated security configuration and vulnerability assessment, not a comprehensive supply-chain mapping tool.

• Security
• Availability
• Processing integrity
• Confidentiality
• Privacy

• Whether controls are suitably designed, and
• Whether they operated effectively over a period of time

• Scanning is not essential during a power outage.
• A scanner can consume UPS battery power without helping the user save cloud documents or shut down safely.
• The UPS should be reserved for the computer, monitor, and necessary network equipment.
• The surge protector helps protect the scanner from voltage spikes, but it will not keep it running during an outage.

• Maximum response and resolution times
• Expected uptime or availability
• Performance requirements
• Escalation procedures
• Consequences for failing to meet requirements

• SOW: Defines a project’s scope, tasks, deliverables, and schedule.
• MOA: Documents specific responsibilities agreed upon by two parties.
• MOU: Records a general understanding or intent to cooperate.

• RTO is how quickly service must be restored.
• RPO is how much data loss is acceptable.

• Snapshots: Restore points may be older and require restoration time.
• On-site backups: Usually require rebuilding or restoring systems, producing higher RTO/RPO.
• Journaling: Records database changes and can reduce data loss, but it still generally requires recovery or replay operations; it does not by itself provide the fastest service restoration.
• Hot site: Designed for rapid failover and minimal data loss.

• Confirming the data has the required columns and data types
• Handling missing or duplicate records
• Converting data into a suitable format
• Selecting or engineering useful features
• Splitting it into training, validation, and test sets

1. Prepare the training data
2. Select an algorithm or configure AutoML
3. Train the model
4. Evaluate its performance
5. Tune hyperparameters if needed
6. Deploy the model

• Controlar o fluxo de dados entre S3 e SageMaker;
• Aplicar regras de segurança por meio da VPC;
• Reduzir a exposição dos dados;
• Permitir acesso privado ao bucket do S3.

• Amazon Inspector: avalia vulnerabilidades, mas não gerencia o fluxo de dados.
• Amazon Macie: ajuda a descobrir e proteger dados sensíveis no S3, mas não cria a conexão com o SageMaker.
• S3 Glacier Deep Archive: é uma classe de armazenamento para arquivamento, não uma solução de conectividade.

• Static IP address: Not needed if the workstation already has network connectivity.
• Subnet mask: Incorrect subnetting would usually prevent local communication, including pinging the server.
• Default gateway: Primarily affects communication outside the local network; it does not normally prevent finding an internal domain controller.

• A. PsFile — Correct: Displays files opened remotely on a system. This reveals shared resources and user activity.
• B. UserInfo — Correct: Gathers information about user accounts, supporting account and privilege enumeration.
• C. PsPasswd — Answer key lists it: This is questionable. PsPasswd is primarily used to change passwords remotely, not enumerate information. The key may classify it broadly as a Windows account-management tool, but it is not a strong enumeration example.
• D. WinSSLMiM — Incorrect: Used for SSL man-in-the-middle activity, not enumeration.

• The Azure DevOps (Boards only) connector is designed specifically for Azure DevOps Analytics views.
• It authenticates directly to Azure DevOps and lets you select an existing Analytics view.
• Filters defined in the Analytics view are applied by Azure DevOps before Power BI retrieves the data, reducing the amount of data transferred.

• Azure DevOps Server (Boards only) is for on-premises Azure DevOps Server.
• OData Feed can consume OData endpoints, but it is not the dedicated Azure DevOps Analytics-view connector.
• OData queries are not the intended dedicated connector for this requirement.

• Honeypots: Decoy systems or services designed to attract attackers. Legitimate users should not access them, so activity there is a strong indicator of compromise.
• DNS sinkholes: Redirect malicious or suspicious DNS requests to a controlled destination. This can identify infected systems attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it is not an attacker-detection method.
• CI/CD: Automates software development, testing, and deployment.
• Threat modeling: Identifies potential threats and weaknesses before or during system design; it does not directly detect an active infiltrator.
• Data obfuscation: Makes information harder to understand, but does not identify attackers.

• C — Some risks cannot be eliminated.

• D — Accepting residual risk does not imply recklessness.

• E — Most companies in this industry will say something similar.

• B: Não é preciso implantar o modelo em um endpoint do Amazon SageMaker, pois o Bedrock já oferece a infraestrutura de inferência.
• C: O SageMaker Model Registry é usado para gerenciar modelos no SageMaker, não é requisito para modelos customizados no Bedrock.
• D: Não existe uma etapa geral de “conceder acesso” ao modelo customizado como requisito principal de uso. O ponto essencial é adquirir o Provisioned Throughput.

• Virus signatures: Associated primarily with antivirus or antimalware tools.
• Security agent deployment: Usually handled by endpoint-management or endpoint-detection-and-response tools.
• Vulnerability scanning: Performed by vulnerability-management or vulnerability-scanning tools.

• Virtual machines
• Virtual storage
• Virtual networking
• Compute resources

• Security as a Service: Provides security functions, not general VM infrastructure.
• Platform as a Service (PaaS): Provides a managed application-development platform, with less control over the underlying VMs.
• Software as a Service (SaaS): Delivers complete applications to users rather than infrastructure for hosting VMs.

• Storage usage of files stored in Microsoft Teams: SharePoint site usage report

• Number of active users per team: Microsoft Teams usage report

1. SharePoint site usage report
2. Microsoft Teams usage report

• A — Capacity: The system must handle all current records and anticipated future records. A system that cannot cope with volume will quickly become ineffective.
• C — Accuracy: Academic records are critical, so the new system must be at least as accurate as the existing system and comparable systems. Poor accuracy could cause serious administrative and reputational problems.
• D — Integration: Linking with the university’s financial systems supports consistency and avoids duplicate data entry, especially for registration, deregistration and fee-related transactions.

• B — Parallel running: This is a useful implementation and risk-control technique, but it is not an essential feature of the system itself. It may also be expensive and time-consuming.
• E — Internet access for all information: This creates significant confidentiality and security risks. External access might be needed for selected services, but unrestricted access to all information is not essential and would be inappropriate for student records.

• A script of cloud CLI commands: IaC because the commands can be saved, reviewed, versioned, and rerun consistently.
• Manually run curl commands: Not necessarily IaC; they are manual actions unless organized into an automated script.
• A sequence of REST requests passed to an API: Could represent automation, but the wording does not explicitly say they are stored and executed as reusable code.
• Commands entered into a cloud console: Manual operation, not IaC.

• A — Tables
• B — Named file formats
• C — Schemas
• E — Databases

Why these are correct

• Tables: Can be cloned using CREATE TABLE ... CLONE. The clone initially uses zero-copy cloning, so storage is shared until changes are made.
• Named file formats: Can be cloned as database objects, preserving the file-format definition.
• Schemas: A schema and its eligible objects can be cloned.
• Databases: A database and its eligible schemas and objects can be cloned.

Why the others are incorrect

• Shares: A share is an account-level data-sharing object, not a normal cloneable database object.
• Users: Users are security principals and cannot be cloned with CLONE.

• Instant messaging/chat: Can be abused to send malicious links or attachments, but P2P file sharing is the more direct high-risk source.
• E-mail: A common malware delivery method, but this question specifically emphasizes an application type associated with direct file exchange.
• End-to-end applications: This describes communication protection or architecture, not a specific application category known for malware distribution.

• Distinct values = 69

• Unique values = 4

• Domínios personalizados.
• Armazenamento suficiente.
• Instâncias dedicadas.
• Balanceamento de carga.
• Menor custo entre os planos que atendem a tudo.

• Due diligence: Researching and evaluating a third party before entering or continuing a business relationship.
• Internal audit: Evaluates controls within the organization itself.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A formal statement or report—such as a SOC 2 report—provided by an independent party about an organization’s controls.

• Azure Machine Learning Studio is designed to build, test, train, and deploy machine-learning models, including predictive analytics.
• Azure Cosmos DB is a globally distributed NoSQL database. It can store data used by an AI solution, but it is not the primary service for developing and deploying predictive models.
• Therefore, the appropriate recommendation is Azure Machine Learning Studio, as shown in Question 15.

• Amazon SageMaker — charges apply for compute, storage, and other resources used.
• AWS Config — generally charges for configuration recording and rule evaluations.
• Amazon CloudWatch — has a limited free tier, but many metrics, logs, alarms, and API usage can incur charges.

• C. The agent orchestration method
• D. The average session time per agent

• Orchestration method: Classic and generative orchestration can have different processing and credit-consumption patterns. Changing the method can affect estimated operating costs.
• Average session time: Longer sessions generally involve more interaction processing, which affects projected usage, credits, and ultimately ROI.

• GPT models used: Important for technical design, but not the primary usage-estimator factor identified in this scenario.
• Average characters in a chat message: Message length alone is not the key business-use projection requested here.

• Minimum
• Maximum
• Average
• Count
• Null/empty values
• Distinct values

• Enable column profile
• Enable details pane
• Show column profile in details pane

• MFA adds an additional authentication factor, such as a phone notification or verification code.
• It helps prevent unauthorized sign-ins, even if a password is compromised.
• It does not encrypt, store, or protect credentials used by deployment processes.

1. x = -100
2. -100 < x < 100
3. 100 = x < 1000
4. x = 1000

• -500 ? class 1
• 0 ? class 2
• 100 ? class 3
• 1000 ? class 4

• Self-signed certificate — Causes a certificate trust warning, not incorrect name resolution.
• Nameserver record — A DNS record problem would usually affect multiple users, unless only this computer uses a different DNS server.
• IP helper — Relays certain network services, commonly DHCP, between subnets; it does not normally determine website name resolution.

• A. Periodically rotate responsibilities: May reduce some risks, but it does not directly detect unauthorized changes.
• B. Review segregation-of-duties conflicts: Identifies incompatible access combinations, not whether a specific data change was unauthorized.
• C. Log changes in an outside application: Logs provide evidence, but someone must review and analyze them. Logging alone does not detect misuse.
• D. Independent review: Directly detects unauthorized changes and reduces the risk that the person making the change can conceal it.

• terraform init is normally required first, especially for a new or changed working directory. It installs providers/modules and configures the backend.
• terraform plan previews the proposed changes.
• terraform apply applies those changes. It also creates a plan internally if you have not supplied a saved plan.

text 
terraform init 
terraform validate       # optional but recommended 
terraform plan 
terraform apply

• Penetration test: Tests for exploitable vulnerabilities; it does not provide a broad opinion on whether security controls operate effectively.
• Annual self-assessment: Not independent, so it provides less assurance.
• Allow each client the right to audit: Inefficient because every customer may conduct a separate audit, creating duplicated effort and disruption.

• HTTPS: Secure web traffic, not general command-line server administration.
• SNMPv3: Secure network monitoring and management, not interactive server login.
• RDP: Provides graphical remote desktop access. It can be secure, but it is not the direct replacement for Telnet in this scenario.
• SMTP: Used to send email.

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• Sales process: Controls which Opportunity Stage values are available.
• Record type: Associates the appropriate sales process with a business scenario and controls available picklist values.
• Page layout: Controls which fields are displayed and whether they are required or read-only.

• Energy Market Team 1 ? Record Type 1, Sales Process 1, Page Layout 1
• Energy Market Team 2 ? Record Type 2, Sales Process 2, Page Layout 2
• Services/Installation Team ? Record Type 3, Sales Process 3, Page Layout 3

• Firewalls and routers
• Servers and applications
• Endpoint devices
• Authentication systems
• Cloud services

• Centralized log collection
• Event correlation
• Dashboards and reporting
• Alerting
• Compliance support

• 10.2.1.0 — network address
• 10.2.1.1 — usable host
• 10.2.1.2 — usable host
• 10.2.1.3 — broadcast address

• API tool matcher: runs a deterministic normalization command after the API tool returns.
• Write/Edit matcher: checks whether the target path begins with src/api/ and runs the linter.

json 
{ 
  "hooks": { 
    "PostToolUse": [ 
      { 
        "matcher": "api_tool", 
        "hooks": [ 
          { "type": "command", "command": "normalize-to-snake-case" } 
        ] 
      }, 
      { 
        "matcher": "Write|Edit", 
        "hooks": [ 
          { "type": "command", "command": "lint-if-under-src-api" } 
        ] 
      } 
    ] 
  } 
}

• Honeypots are deliberately vulnerable or attractive systems designed to lure attackers. Legitimate users should not normally access them, so activity there can indicate a successful intrusion or lateral movement.

• A DNS sinkhole redirects requests for known malicious domains to a controlled internal system instead of the real destination. Security teams can monitor those requests and identify compromised devices attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it is a protection method, not an attacker-detection method.
• CI/CD: Automates software development and deployment processes.
• Threat modeling: Identifies potential threats during design and planning.
• Data obfuscation: Makes information harder to understand, but does not directly detect infiltrators.

• Red team: Simulates attackers and tests exploitability.
• Blue team: Defends, monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve cooperation and defenses.
• White team: Manages and oversees the rules, scope, and authorization of the exercise.

• Reconnaissance: Gathering information about the target.
• Weaponization: Creating or combining a malicious payload with a delivery method.
• Delivery: Sending the payload, such as through phishing.
• Exploitation: Triggering a vulnerability or weakness to gain execution or access.

• JDBC
• SnowSQL
• Snowflake Web Interface (UI)
• ODBC
• Python connector

• Proxy server: Acts as an intermediary for requests, but does not necessarily provide an encrypted connection to the corporate network.
• NGFW: A firewall with advanced inspection and filtering capabilities; it may support VPNs but is not the remote-access solution itself.
• Security zone: A logical network grouping based on trust or security requirements, not a method for remote access.

1. Open the Offenses tab

1. Open the offense details

1. Review contributing events

1. Analyze the attack chain

1. Investigate the assets

1. Validate and respond