Huawei H12-311_V3.0 Exam Prep
HCIA-WLAN V3.0 (Page 6 )

• B: Prompt caching reduces cost and latency for repeated content, but cached content still occupies the context window. It does not solve context accumulation.
• C: Switching to a smaller model changes model capacity but does not address the growing context or remove irrelevant data.
• D: Keeping everything indefinitely increases token usage, risks context-window limits, and can distract the model with outdated information.

• Response and resolution times
• Availability or uptime requirements
• Performance targets
• Support responsibilities
• Penalties or remedies if requirements aren’t met

• SOW (Statement of Work): Describes the work, deliverables, scope, and schedule for a project.
• MOA (Memorandum of Agreement): Documents agreed-upon responsibilities or cooperation between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, often without detailed enforceable service targets.

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or financial impact to another party, such as through insurance or a contract.
• Mitigate: Reduce the likelihood or impact using controls, such as firewalls, training, or backups.
• Avoid: Eliminate the activity that creates the risk.

• Separate development, test, and production environments
• Building components in unmanaged solutions during development
• Organizing solutions by functional area
• Exporting and deploying managed solutions to production
• Validating changes before production deployment
• Preventing developers from overwriting one another’s production changes

• delta.logRetentionDuration
• delta.deletedFileRetentionDuration

• delta.deletedFileRetentionDuration controls how long physically deleted or obsolete data files are retained before they become eligible for removal by VACUUM. Set it to interval 30 days.
• delta.logRetentionDuration controls how long Delta transaction-log history is retained. Set it to interval 30 days to support audits and time travel for that period.

sql 
ALTER TABLE Catalog1.Schema1.Table1 
SET TBLPROPERTIES ( 
  'delta.logRetentionDuration' = 'interval 30 days', 
  'delta.deletedFileRetentionDuration' = 'interval 30 days' 
);

• Internal audit: Reviews the organization’s own controls and processes.
• Penetration testing: Actively tests systems for exploitable vulnerabilities.
• Attestation: A SOC 2 report is an attestation product issued by an independent auditor, but the analyst is not performing the attestation. They are reviewing it as part of vendor evaluation.

• Lower order numbers appear first.
• For example, a variable with order 100 appears before one with order 200.
• The Sequence field is not the control used for catalog variable display order.
• The Default Value sets a value, not placement.
• The Choice field defines selectable options, not the variable’s position.

• B. Versioned configuration files — Infrastructure is defined in machine-readable files and tracked in version control, allowing repeatable provisioning and change history.
• D. Docker files — Assuming “Doctor files” is a typo for Dockerfiles, a Dockerfile declaratively defines how to build a container image and is commonly considered infrastructure/configuration as code.

• A. Cloned virtual machine images — These are prebuilt infrastructure artifacts, but cloning an image is not itself a code-based infrastructure definition.
• C. Change management database records — A CMDB records information about infrastructure; it does not define or provision that infrastructure.

• Input validation: Prevents malicious or malformed input within an application; it does not authenticate a software package.
• Secure cookies: Protect web-session cookies; they do not protect downloadable software.
• Fuzzing: Tests software by supplying unexpected input to find vulnerabilities; it does not verify software integrity.

• 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

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

• The audience and stakeholders
• The complexity and type of requirements
• The communication method and level of detail needed
• Whether to use diagrams, models, documents, demonstrations, or slides

• B: Authority to host the presentation is not the key preparation activity.
• C: Stakeholder sign-off may occur later; presenting requirements does not always require formal approval beforehand.
• D: A scribe may be useful in a meeting, but hiring one is not a core preparation requirement for presenting.

• 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

1. System prompts can authorize users — No

1. System prompts can reduce TPM consumption — Yes, with qualification

1. System prompts guide generative AI behavior — Yes

• Regression predicts continuous numeric outcomes, such as house price, temperature, or sales amount.
• Linear regression assumes the target can be estimated from a linear relationship between the input features and the target.
• In Azure Machine Learning, you use a labeled dataset containing:

• Classification predicts a category or class, such as “spam” or “not spam.”
• Clustering groups similar records without a known label; it is an unsupervised learning technique.

• Escape to host: A virtualization attack where code escapes a guest VM and accesses the host system. Nothing in the scenario mentions virtualization.
• Browser extension: Can redirect or manipulate web-browser traffic, but not normally database-server traffic.
• Valid accounts: Describes using stolen or compromised credentials, not redirecting network traffic.
• Process injection: Injecting malicious code into a legitimate database or networking process could allow an attacker to alter how that process handles outgoing traffic.

• IDS attack signatures: Primarily detects suspicious network activity; it is not the best control for scanning uploaded documents.
• Load balancer: Distributes traffic and can improve availability, but does not inspect files for malware.
• WAF: Helps block web attacks such as command injection and SQL injection, but it is not primarily a malware-scanning solution.

• SOSL searches text across objects and is not appropriate for selecting Account table columns.
• describeSObjects() provides metadata about objects and fields, but it does not itself build or execute the query.
• Dynamic Schema binding supports runtime determination of object and field information, which is required here.
• REST API is unnecessary because this is being implemented in Apex.

• Business
• People
• Governance
• Platform
• Security
• Operations

• Sustainability
• Performance efficiency
• Reliability

• Internal hostnames and subdomains
• Network structure and naming conventions
• Servers and services
• Relationships between systems

• Determining ISP-assigned address space: Usually involves external registration and DNS information, not internal host discovery.
• Bypassing DNS sinkholing: Would require evidence that malicious DNS requests avoided redirection.
• Initial access: DNS queries alone do not show that the attacker gained access.
• Exfiltrating data: DNS tunneling can do this, but the snippet would typically show encoded or unusually long DNS queries.

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

• Red team: Offensive security; simulates attackers and validates exploitability.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Helps red and blue teams collaborate and improve defenses; not usually the primary testing role.
• White team: Oversees and coordinates the rules, scope, and authorization of an exercise.

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

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

1. Open Notepad as Administrator.
2. Open:

1. Remove or correct the line mapping the website to the wrong IP address.
2. Save the file.
3. Optionally run:

cmd 
   ipconfig /flushdns

1. Write a structured log entry to CloudWatch Logs containing:

1. Create a CloudWatch Logs metric filter that:

text 
ApiRequests 
Operation=GetOrders 
ResponseCode=500 
Version=2.4.0

• B is incorrect: CloudWatch Logs Insights queries analyze logs but do not directly publish metrics in this manner.
• C is incorrect: ALB access logs do not contain arbitrary Lambda response metadata as custom fields.
• D is incorrect: X-Ray traces and insights are not the appropriate mechanism for creating these custom, dimensioned application metrics.

• 50% memory utilization baseline: The environment can be provisioned with excess capacity, leaving room for growth and workload spikes.
• Storage scalability: Cloud storage can generally be expanded as needed without redesigning the physical platform.
• Single circuit failure resilience: A properly designed IaaS provider uses redundant power circuits and infrastructure, so failure of one circuit should not take the platform offline.

• A — Dual PDUs: Helps with power redundancy but does not provide storage scalability.
• C — Network load balancing: Provides network-path resilience, not memory or storage scalability, and does not address a power-circuit failure.
• D — Multiple NAS devices: May improve storage capacity, but does not inherently provide power resilience or the required compute-capacity baseline.

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

• Deterrent control: The signs warning people they may be filmed discourage unauthorized or malicious behavior. They may prevent incidents by influencing behavior, but their primary purpose is to deter.
• Detective control: The CCTV system monitors and records activity so security personnel can identify suspicious or unauthorized actions.

• Preventive: Blocks or prevents an incident, such as a lock or access-control system.
• Corrective: Fixes or restores systems after an incident.
• Directive: Tells people what they must do, typically through policies or procedures.
• Compensating: Provides an alternative control when the preferred control cannot be used.

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

• Help the team identify the root causes of delays.
• Empower the team to improve its workflow and practices.
• Facilitate removal of impediments.
• Avoid directing the team toward a solution without its involvement.
• Protect quality and sustainable delivery rather than simply accelerating everything.

• A: An impediment log may help, but merely recording problems does not empower the team to solve them.
• B: Directing the team to solutions conflicts with self-management.
• C: Adding impediments to the product backlog may incorrectly treat internal obstacles as product features and delays their resolution.

• A. Continue using the current system: It will eventually fail and offers no recovery strategy.
• B. Virtualize the entire system: Correct. A VM can preserve the old OS, application, settings, and dependencies while running on newer physical hardware.
• C. Containerize the application: Containers generally share the host OS kernel and are not suitable for preserving an entire incompatible legacy OS.
• D. Clone the disks to USB: A disk clone may provide backup or temporary recovery, but it does not solve hardware compatibility or provide a reliable long-term platform.

• Review the risk register.
• Check the documented risk response strategy, such as using a backup resource, reallocating work, or adjusting sequencing.
• Implement the planned response promptly.

• B: Moving the task may affect the critical path and should not be done without first evaluating the planned response and impacts.
• C: Excluding a required task would change scope and business requirements without proper analysis or approval.
• D: Updating lessons learned and the risk log may be appropriate later, but it does not address the immediate problem. First, execute the response.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

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

• FTP — Transfers files using a client/server model and supports authentication. It uses separate control and data connections.
• TFTP — A very simple file-transfer protocol with no authentication and minimal features. Commonly used to transfer router or switch configuration files and IOS images.
• SCP — Securely copies files over SSH. It provides encryption and authentication.
• SFTP — Also transfers files securely through SSH, but provides more file-management capabilities than traditional SCP.
• HTTP/HTTPS — Primarily web protocols, but can also download files; HTTPS encrypts the session.

• TFTP = simple, unauthenticated file transfer
• FTP = file transfer with authentication, but not inherently encrypted
• SCP/SFTP = secure file transfer using SSH

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

Why this is correct

• Each user authenticates with their own Google account.
• Google manages the user’s SSH key association.
• IAM controls who can access instances.
• Access can be audited by user identity, so security can determine who accessed a VM.
• Granting the role to a Google group avoids managing permissions individually.

Why the others don’t apply

• A: A shared private key is difficult to distribute securely and cannot reliably identify which employee used it.
• B: Manually collecting and deploying keys on every instance is operationally inefficient and complicates auditing.
• D: A project-wide shared key has the same identity and key-management problems as option A. It also does not provide per-user accountability.

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

• The job keeps 31 days of regular restore points. A backup from the week of January 1 is older than 31 days by March 20, so it is no longer expected to remain on the performance tier.
• It is also a weekly GFS full backup, retained for 14 weeks. Therefore, it is still protected and has not been deleted.
• In a Scale-out Backup Repository, older backups can be moved from the performance tier to the capacity tier—typically object storage—according to the configured offload policy.
• The archive tier is not selected because the question’s configuration does not indicate that the backup has been archived there.

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

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

• 10 minutes have elapsed, or
• 20 MB of accounting data has accumulated

• Deterministic approve/reject results
• Strict adherence to predefined rules
• Consistent, reproducible outcomes
• Auditability and regulatory compliance

• Base table — the table containing common inherited fields
• Parent table — the table directly extended by the child
• Other tables in the hierarchy

• Company documents
• Databases
• Knowledge bases
• Current web or business data

• A: Describes diversity and inclusive design, not grounding.
• B: Describes explainability or model interpretability.
• D: Describes documenting a model’s capabilities and limitations.

• Where to find the TiMOS runtime image
• Which configuration file to load
• The IP address and related settings for the CPM management Ethernet port

• A: User authorization is configured in the router’s security configuration, not primarily in the BOF.
• C: Hardware initialization is performed by the boot process and system software.
• D: The system date and time are configured separately, often through NTP or CLI settings.

• Normal or expected input
• Boundary values
• Invalid input
• Potential error conditions

• A is incorrect: it creates test code, not detailed test documentation.
• C is incorrect: it does not primarily integrate external testing frameworks.
• D is incorrect: executing tests requires your development environment or test runner.