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

• Correct answer: LACNIC (A)

• Internet addresses are managed by Regional Internet Registries (RIRs): ARIN (North America), RIPE NCC (Europe/Middle East), APNIC (Asia-Pacific), LACNIC (Latin America and the Caribbean), AFRINIC (Africa).
• Panama is in Latin America, so the IP’s registration would be in LACNIC.
• Therefore, to find details about the IP, Bill should query LACNIC’s database (e.g., via a whois query or a LACNIC WHOIS web service).

• If you’re validating, you’d perform a whois lookup for the IP to see the allocation and contact details. Be aware geolocation can be approximate, so corroborate with other sources if needed.

• Red team: Offensive security; attempts exploitation and simulates attackers.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve defenses, but is not the best direct answer here.
• White team: Usually oversees or coordinates an exercise, including rules of engagement and scope.

• Note the question number before leaving—for example, Question 38.
• Use the exam’s question navigator or Back/Previous button to return to that number.
• If you close or refresh the page, your position may not be saved, depending on the site. Reopen the page and select the question number again.
• Avoid using the browser’s Back button if it causes the exam page to reload; use the exam’s built-in navigation instead.

• Unrestricted data mining: Data mining is not automatically a privacy violation. It becomes an issue when personal data is collected or used improperly.
• Identity theft: This is a possible consequence of inadequate privacy protection, but it is not the central focus of privacy regulations.
• Human rights protection: Privacy can be considered a human right, but this option is broader than the specific regulatory focus.
• Identifiable personal data: Regulations such as HIPAA focus directly on controlling the collection, use, disclosure, and protection of personal information.

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.

• Row counts
• Minimum and maximum values for columns
• Distinct-value information
• Other characteristics used for optimization

• Fine-tuning requires a properly formatted training dataset.
• For classification or instruction-style fine-tuning, examples are supplied in JSONL format.
• Each line represents one training example, typically containing the input prompt and the desired completion or label.
• The file must then be uploaded or made available to the Microsoft Foundry fine-tuning workflow.

• A: Prompt Flow is useful for prompt experimentation, but it is not required to start fine-tuning.
• B: You do not need to deploy the base model to an online endpoint before fine-tuning.
• C: Tracing supports observability and evaluation, but it does not prepare the fine-tuning job or dataset.

• Maintain head office control: Transfer pricing generally supports decentralisation rather than direct head-office control.
• Establish centralised decision making: This conflicts with divisional autonomy.
• Develop a top-down culture: Transfer pricing is intended to support empowered divisions and goal congruence, not impose purely top-down management.

• Tokens: Individual units of text processed by a model, such as words, subwords, or characters.
• Models: Systems that learn patterns and generate predictions or outputs.
• Binaries: Data represented using the binary number system, not semantic representations.

• Footprinting is reconnaissance used to map an organization’s network, hosts, naming conventions, and services.
• A name such as fshare.int.complia.org suggests an internal file-sharing host (fshare) and an internal naming structure (int).
• This can reveal useful information to an attacker before attempting exploitation.

• ISP-assigned address space: Usually determined through public registration and DNS data, not an internal hostname.
• DNS sinkhole bypass: Would involve avoiding redirected malicious-domain queries.
• Initial access: DNS reconnaissance alone does not compromise the server.
• Data exfiltration: DNS tunneling typically generates many encoded or unusually long subdomain queries, not simply a meaningful internal hostname.

• A — Improved management of storage space: Correct.

• B — Improved supplier relationships: Correct.

• C — Improved pricing decisions: Correct.

• D — Non-product-specific costs must be apportioned: Incorrect.

• E — Profitability of each customer group: Incorrect.

• Key-based authentication: Provides an endpoint secured with API keys.
• Real-time REST access: Supports online inference through an HTTP/REST endpoint.
• No VM vCPU quota consumption: Microsoft hosts and manages the underlying infrastructure, so your subscription’s VM quota isn’t used.

• Batch: Intended for asynchronous, large-volume processing rather than real-time requests.
• Self-hosted container: You manage the infrastructure and typically need compute resources and quota.
• Standard: This is not the clearest deployment type for the stated requirements; the specific Foundry option is serverless API.

• Scale out during the hours when customer traffic is high.
• Scale in during low-demand periods, reducing instance-hours and cost.
• Use scaling policies based on metrics such as CPU utilization or request count.

• Multiple Availability Zones: Improves availability and fault tolerance, but does not automatically reduce cost.
• Placement group: Helps with specialized performance or low-latency requirements, not cost optimization.
• Private subnets: Improve network security, but do not automatically adjust capacity or reduce EC2 usage costs.

• Labels control access and protection, not blanket exclusion.
• If the user has permission to open a labeled file—especially if the label allows authenticated users to view it—Copilot can use that file in a summary.
• If the label applies encryption and the user lacks the required usage rights, Copilot should not use the file or reveal its contents.
• Copilot honors the user’s existing permissions, so it should not expose labeled content to an unauthorized user.

• B — Notify affected business units: Notification should follow an initial determination of scope and impact; otherwise, the organization may communicate incomplete or inaccurate requirements.
• C — Assess noncompliance risk: Risk assessment requires understanding the regulation’s requirements first.
• D — Inform senior management: Management should be informed, but with a clear summary of the regulation’s impact, risks, and recommended actions.

• B — Sales staff will tender for riskier contracts:

• C — Sales staff will encroach on other territories:

• D — Sales staff will look for new jobs:

• 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.

1. Initiation

1. Planning

1. Execution

1. Monitoring and controlling

1. Closing

• Disable high concurrency: Changes workspace-wide behavior and is not the targeted way to isolate these workloads.
• Modify the number of executors: Adjusts capacity and performance, but does not provide workload isolation.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• Business risks
• Potential financial, operational, legal, or reputational impact
• How governance reduces risk to organizational objectives
• How much risk the organization is willing to accept

• 24 cores: Available in the Business Critical provisioned-compute configurations.
• Approximately 124 GB memory: Matches the memory capacity of the relevant Business Critical hardware configuration.
• More than 50,000 IOPS: Business Critical uses local SSD storage and provides the high I/O performance required here.
• 500 GB storage: Well within the tier’s supported capacity.

• Premium: The DTU-based Premium tier does not provide the required combination of compute, memory, and I/O characteristics.
• Hyperscale: Hyperscale is primarily intended for very large databases and independent storage scaling. It is not the best match for these specific high-memory and high-IOPS requirements.

• A — If there is no demand, there should be no production.

• B — Not all sales equal profit.

• C — Stocking up on inventory is bad for business.

• D — All costs, except materials, are considered fixed.

• E — Departments should operate at full capacity regardless of bottlenecks.

• Defender for Servers is the Defender for Cloud plan that protects Azure VMs and generates security alerts that can be reviewed in Defender for Cloud.
• Azure Diagnostics extension collects guest OS monitoring data, but it does not onboard VMs to Defender for Cloud or provide Defender security alerts.
• Data connectors are used for Sentinel integrations.
• Azure Storage Analytics and workflow automation do not provide VM protection.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity; it is not the best control for scanning uploaded documents for malware.
• C. Load balancer: Distributes traffic among servers and improves availability, but does not inspect files for malware.
• D. WAF: Protects web applications against attacks such as SQL injection and command injection. It may help secure the upload function, but malware scanning is the key requirement here.

• # Development
• # Testing
• # Production

• Separate endpoints: relate to compute or connectivity, not dashboard labels.
• Separate queries: retrieve or transform data but do not designate visual sections.
• Direct text written into the dashboard in editing mode: dashboards use text boxes, typically with Markdown formatting, rather than arbitrary text placed directly on the canvas.

• The Intune device limit restriction does not apply in the normal way; DEM enrollment supports up to 1,000 devices.
• However, the Microsoft Entra maximum number of devices per user setting can still impose a limit when the enrollment creates an Entra device object.
• Therefore, a DEM account is not automatically unlimited. The effective limit depends on the Entra device setting and the enrollment/join type.

• Economy: Obtaining inputs at the lowest appropriate cost.
• Efficiency: Making the best use of resources, such as staff, money, and equipment.
• Effectiveness: Achieving the intended objectives or outcomes.

• CPU: Number of virtual CPUs and, where applicable, CPU reservations.
• Memory: Amount of memory and memory reservations.

• Network interface: Usually configured through the VM or workload networking configuration.
• PCI devices: Specialized hardware and not a standard VM Class resource in this context.
• Storage: Typically selected through storage policies or the VM’s storage configuration.

• Un AG puede tener réplicas en Windows y Linux desde SQL Server 2017; por tanto, una réplica Windows y otra Linux es posible.
• Sin embargo, las réplicas de un AG deben utilizar normalmente la misma versión principal de SQL Server. Una instancia SQL Server 2017 no puede tener directamente una réplica secundaria SQL Server 2019 como configuración normal y permanente.
• En tu escenario, SQL Server 2017 en Windows y SQL Server 2019 en Linux no se pueden añadir directamente como réplicas equivalentes de AG1. Primero habría que realizar un proceso de actualización/migración compatible, por ejemplo mediante una actualización gradual o una tecnología de migración como log shipping o distributed availability groups, según el diseño.

• Tipo de clúster y mecanismo de quorum.
• Failover normalmente manual en configuraciones multiplataforma.
• Edición y características compatibles.
• Configuración de endpoints y permisos.
• Limitaciones específicas de SQL Server en Linux.

• Crash cart: Provides local physical access, not remote access.
• Jump box: A secured intermediary used to reach devices over the normal network; it may be inaccessible if the appliance has not booted.
• Secure Shell (SSH): Requires the device’s operating system and network services to be running properly.

• Disabling a compromised account
• Blocking a malicious IP address
• Isolating an endpoint
• Creating or escalating an incident ticket

• Virus signatures: Primarily associated with antivirus or endpoint protection.
• Security agent deployment: Usually handled by endpoint-management or security-agent platforms.
• Vulnerability scanning: Typically performed by vulnerability-management tools.

• Formatting: May remove file-system references but often leaves recoverable data.
• Degaussing: Uses a magnetic field to erase data, but can damage or make magnetic drives unusable.
• Defragmentation: Rearranges data for performance; it does not securely erase information.

• Attack simulator — Used to run phishing and other attack simulations for user awareness training.
• Hunting — Used to proactively query security data and investigate potential threats.
• Incidents — Used to investigate and manage related alerts and active security events.

• The server accepts unauthenticated image uploads, which creates an opportunity for an attacker to upload a malicious script disguised as an image or using an unexpected file type.
• A web shell is a malicious script placed on a web server that gives an attacker remote command execution through web requests.
• The suspicious process and outbound connection to a low-reputation IP are consistent with the attacker using the web shell to execute commands or establish communication with command-and-control infrastructure.

• Worm: Usually self-propagates across multiple systems; the scenario focuses on the upload page.
• Cryptocurrency mining: Possible, but there is no indication of resource-intensive mining activity or insider involvement.
• Rootkit Trojan over RDP: The evidence points to the vulnerable upload functionality, not an exposed RDP service.

1. Create Workspace2 with Lakehouse2 — F
2. Migrate the Employee table to Lakehouse2 — E
3. Assign the data engineer the Contributor role for Workspace1 — D

Why

• Sharing Lakehouse1 would not provide the required isolation.
• Viewer access would not allow writing to Customer.
• Giving Contributor access to Workspace2 would expose the sensitive table.

• 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.

• Frequency/likelihood = how often or how likely the risk is to occur.
• Severity/impact = how damaging or costly the consequences would be.

• A minor equipment fault occurring frequently may have high frequency but low severity.
• A major cyberattack occurring rarely may have low frequency but high severity.
• A risk that happens often and causes substantial losses has high frequency and high severity.

• Menerjemahkan soal ke bahasa Indonesia.
• Menyebutkan jawaban yang benar.
• Menjelaskan alasan jawaban tersebut.
• Memberi tahu jika kunci jawaban yang tersedia tampaknya keliru.
• Menjelaskan istilah teknis penting dalam soal.

• Shared capacity

• Fabric capacity — F SKUs

• Fabric trial capacity

• Existing Power BI Premium — P SKUs

• The table is large.
• Queries frequently filter or join on particular columns.
• The table’s natural data order does not support good micro-partition pruning.
• Clustering improves performance enough to justify its maintenance cost.

1. Clear principles and boundaries — Employees have freedom, but decisions must remain within clear organizational values, policies and limits.
2. High degree of freedom — Managers are trusted to make decisions rather than seeking continual approval from senior management.
3. Frontline customer responsibility — Customer-facing managers should be empowered to manage customer relationships and respond quickly to needs.
4. Transparent and ethical information — Information should be openly available and used honestly, supporting trust and informed decision-making.

• Determine the project budget — Budget development is a separate cost-management activity.
• Develop a communication plan — This belongs to project communications planning, not schedule completion.
• Establish baselines — Baselines are created after the schedule and related plans have been developed and approved. They formally capture the approved plan.

• Dark web: A place where leaked credentials may be sold or shared, not usually the original source.
• Threat feeds: Collections of intelligence about threats, not a typical leakage source.
• State actors: A type of attacker, not an accidental corporate disclosure source.
• Vulnerability databases: Track known vulnerabilities, rather than leaked credentials.

• 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.

• The requirement is an assessment of the Azure environment’s design, which requires a support plan offering proactive architectural guidance.
• Premier support would provide this capability, but it is a high-cost option.
• Since the requirement says to minimize expenses, Premier is not the best recommendation.
• A lower-cost plan with the required advisory/design-review capability—historically Professional Direct in Azure’s support-plan model—would be more appropriate.

• The ERSPAN source is the device or interface whose traffic is being copied.
• The ERSPAN destination is the device receiving the encapsulated copy and forwarding it to the traffic analyzer.
• The local monitor session number is locally significant. Therefore, the source and destination do not need matching session IDs such as 47 or 48.
• The erspan-id identifies the ERSPAN stream and must correspond between the source and destination configuration.

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

• Existing Eventhouse data: remains available only in the KQL database.
• Data ingested after enabling the feature: is copied to OneLake and can be accessed through OneLake file explorer.
• New databases: are irrelevant; the setting applies to the selected KQL database.

• Active remediation actions role in Microsoft Defender for Endpoint

• Security Reader role in Azure AD/Entra ID

• Security Administrator is broader than necessary because it grants extensive security-management permissions, violating least privilege.
• Compliance Data Administrator is intended for compliance data management, not Defender for Endpoint remediation approvals.