Pure Storage Portworx-Enterprise-Professional Exam Prep
Pure Certified Portworx Enterprise Professional (Page 6 )

• 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

• Deterrent control: The signs warning that people may be filmed can discourage unauthorized or malicious activity. They do not directly stop the action; they influence behavior.
• Detective control: CCTV records or monitors activity so security personnel can identify events or investigate them afterward.

• Preventive: Stops an incident from occurring, such as access control.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: An alternative control used when the preferred control is not feasible.

• Self-signed certificate: Causes a browser security warning, not incorrect name resolution.
• Nameserver record: A DNS problem would typically affect multiple users, not just one workstation.
• IP helper: Relays services such as DHCP across network segments; it does not resolve website names.

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

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Moving the risk’s financial impact to a third party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or employee training.
• Avoid: Eliminating the activity that creates the risk.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or its financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact of the risk, such as by implementing security controls.
• Avoid: Eliminate the activity or exposure that creates the risk.

• Architects design overall Splunk infrastructure and data strategy.
• Administrators manage configuration, access, and system operations.
• Knowledge Managers create and maintain knowledge objects such as data models, field extractions, and event types. They may support pivots, but they are not the primary users of them.

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

• httprint fingerprints Web servers by analyzing their HTTP responses. It can help identify the Web server type and sometimes its version, even when the banner has been modified or hidden.
• Wget is mainly used to download files or Web content.
• WinSSLMiM is associated with SSL man-in-the-middle testing.
• Whisker is an older Web-server vulnerability assessment tool, especially associated with IIS, rather than the expected banner-grabbing tool here.

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

• contoso.onmicrosoft.com
• contoso1.onmicrosoft.com

• onmicrosoft.com domains: Maximum of five per tenant.
• Custom domains: Domains that your organization owns and verifies in Microsoft 365.

• Each team’s Bedrock workflow uses a separate IAM service role.
• The role’s Amazon S3 permissions can be limited to only that team’s customer folder or objects.
• This enforces least privilege and prevents one team’s Bedrock application from accessing another team’s data.
• Access is enforced by AWS permissions, not by asking users to provide a customer name in each request.

• A single role with broad S3 access does not provide team-level isolation.
• Asking teams to specify a customer name is not an access-control mechanism.
• Redacting data does not prevent unauthorized access.
• A bucket policy alone is insufficient unless it explicitly enforces the required team-role restrictions.

• Bronze: Raw ingested data
• Silver: Cleaned, validated, and transformed data
• Gold: Business-level data for analytics, dashboards, and reporting

• Endpoint Manager: manages hosts and sensor-related settings.
• Falcon Investigator: supports investigation and analysis, but does not necessarily grant RTR access.
• Remediation Manager: handles remediation-related actions rather than interactive host access.

• Documented and formally requested
• Analyzed for security, cost, and operational impact
• Reviewed and approved by the appropriate personnel
• Tested before implementation
• Tracked and reversible if problems occur

• Risk management process: Identifies and evaluates risk, but does not directly authorize design changes.
• Product design process: Applies primarily while creating or developing the product.
• Design review process: May have identified the issues, but the next step for changing an already released design is controlled change management.

• Malware or malicious software
• Command-and-control tools
• Internet surveillance and intrusion software

• ITAR: A U.S. regulation controlling defense-related articles and services; it is not the international arrangement described.
• Palermo Convention: Focuses on transnational organized crime and related protocols, not export controls for cyber weapons.
• GDPR: European data-protection and privacy legislation.

• A — Windows 11 with Azure CLI installed: Yes

• D — Chrome OS using Azure Cloud Shell: Yes

• E — Windows 10 with the Azure PowerShell module installed: Yes

• B — Linux with only Azure CLI: No, because the option does not state that PowerShell is installed.
• C — macOS with PowerShell Core only: No, because it does not state that Azure PowerShell modules or Azure CLI are installed.

• A password cracker would normally be identified by behavior such as loading password hashes or attempting dictionary/brute-force attacks.
• The question describes a routine audit, not password recovery.
• Simply encountering a protected file during an audit is characteristic of a misconfigured or insufficiently privileged FIM.

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

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.

• Set credit quotas for an account or individual virtual warehouses.
• Define monitoring intervals.
• Trigger actions when usage reaches thresholds, such as sending notifications or suspending a warehouse.
• Help control unexpected warehouse spending.

• Account Usage: Provides historical usage and billing data; it does not enforce credit limits.
• Warehouse Limit Parameter: Not the Snowflake object used for account-wide credit controls.
• Credit Consumption Tracker: Not a standard Snowflake object.

• 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

• Preparing and managing datasets
• Building and training machine-learning models
• Testing and evaluating models
• Deploying models as endpoints for predictions

• Which batches and markets are affected
• Whether the deficiency affects product quality, efficacy, or patient safety
• Whether the issue is an ongoing manufacturing problem
• Whether immediate containment or distribution suspension is needed

• A — Withdraw the product: may be necessary, but is premature before assessing the risk.
• B — “Dear Dr.” letter: may be appropriate later, depending on the risk.
• C — Notify global authorities: may become mandatory, but the scope and urgency depend on the assessment.

• Matching hashes: The software likely has not changed.
• Different hashes: The software was modified or corrupted.

• Encryption: Protects confidentiality by making data unreadable; it does not primarily detect changes.
• Baselines: Define an approved system or configuration state, but they are not the specific integrity mechanism here.
• Tokenization: Replaces sensitive data with substitute values.

Manager role

DAX 
Country[Manager] = USERPRINCIPALNAME()

• Sales
• Human Resources

CFO role

• See sales for all countries
• See no Human Resources data

• Do not restrict the Country table or Sales table.
• Apply a filter to Human Resources that always returns false, such as:

DAX 
FALSE()

• Minimum and maximum values
• Number of distinct values
• NULL information
• Other metadata used for pruning

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

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

• Suspended an operator who refused to use unsafe equipment.
• Paid another operator a bonus for using it.
• Prioritised short-term productivity over employee safety.

• A — Management is not particularly concerned with managing risks.

• B — Employees will perceive that management does not care about health and safety risks.

• C — The factory’s safety record is likely to be poor.

• Determining ISP-assigned address space: Usually involves public reconnaissance, such as WHOIS or regional Internet registry information.
• Bypassing DNS sinkholing: Would require evidence that malicious domains are resolving outside the organization’s sinkhole controls.
• Achieving initial access: DNS log entries alone do not demonstrate compromise or entry.
• Exfiltrating data: DNS tunneling generally involves repeated queries containing encoded or unusually long data, not merely internal host discovery.

• 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

• File is shared externally ? Access level

• File is labeled “Internal only” ? Sensitivity label

• Virus signatures: Primarily associated with antivirus or antimalware tools.
• Security agent deployment: Usually handled by endpoint-management or endpoint-security platforms.
• Vulnerability scanning: Performed by vulnerability-assessment tools, although a SIEM may ingest their results.

• Who owns security risks and decisions
• Who is responsible for implementing controls
• Who reports security performance to management
• How security responsibilities align with business objectives

• B — Compliance with audit requirements: Governance may support compliance, but audit compliance is not its main objective.
• C — Monitoring security incidents: This is an operational security activity, not the central purpose of governance.
• D — Creation of tactical solutions: Governance establishes direction and oversight; tactical solutions belong to management and operational teams.

• Disable high concurrency: This changes session-sharing behavior but does not provide dedicated compute or true workload separation.
• Modify the number of executors: Adjusts resources within a Spark job; it does not isolate bronze and silver processes.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• Sustainability
• Performance efficiency
• Reliability

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

• C. Case after-insert trigger that publishes a Platform Event

• D. Custom Apex controller that publishes a Platform Event

• A. Trigger with a callout: Salesforce triggers should not make direct synchronous callouts, and this tightly couples transaction processing to the external system.
• B. Workflow Rule with Outbound Message: This can react to record changes, but it cannot reliably capture a user clicking a menu item. It also does not provide the same flexible event-driven model as Platform Events.

• If the attachment is safe, it is released to the user.
• If malware is detected, the attachment is blocked or removed according to the policy.
• This reduces delivery delays without disabling malware scanning.

• Replace removes the original attachment and replaces it with a text file explaining that it was blocked. It does not primarily optimize delivery time.
• Block and Enable redirect blocks messages with suspicious attachments and can redirect them for review; it does not provide the required faster delivery experience.
• Monitor and Enable redirect is for observation and does not reliably block malicious attachments.

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

• A user connects with their Google account.
• Google associates the user’s SSH key with that identity.
• IAM roles determine whether they can log in.
• Access can be tied to a specific employee for auditing.
• Removing the IAM role removes their login access.

• compute.osLogin: regular OS login access
• compute.osAdminLogin: OS login with administrative privileges, typically including sudo

text 
enable-oslogin=TRUE

• Custom domains are supported.
• It provides dedicated compute instances.
• It offers enough storage for the applications.
• It supports multiple instances with load balancing between them.
• It is less expensive than higher tiers such as Premium.

• Free and Shared use shared compute and have limited storage, so they cannot meet the dedicated-instance requirement.
• Basic provides dedicated compute and custom domains, but the question’s requirement for the broader multi-instance/load-balancing capability is intended to point to Standard.

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records activity such as login times and resource usage.

• CIA: Confidentiality, integrity, and availability—the three core security goals.
• ACL: Access Control List, which defines permitted or denied traffic or access.
• PEM: A certificate and key encoding format, not the primary function of RADIUS.

• Use the grant-date fair value: $30
• Do not remeasure to the year-end value of $45
• Update the estimate of employees expected to vest

• Dr Share-based payment expense $450,000
• Cr Equity/share option reserve $450,000

• 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

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

• Measurement bias: Errors in how features or labels are measured, such as unreliable camera data or inconsistent labeling.
• Observer bias: A human evaluator’s subjective judgment influencing observations or labels.
• Confirmation bias: Favoring information that supports an existing belief.

Recommended process

1. Access each switch’s terminal.
2. Use help to identify available commands.
3. Use the MAC table command, such as:

text 
   show mac-address-table

1. Use VLAN information, such as:

text 
   show vlan

1. Use interface information, such as:

text 
   show ip interface brief

1. Record each device’s: