Palo Alto Networks PSE-Prisma-Pro-24 Exam Prep
Palo Alto Networks System Engineer - Prisma Cloud Professional (Page 8 )

• A: Describes an update-set conflict, not a Dictionary Override.
• B: Describes a configuration item or change concept.
• C: Describes an approval or workflow activity.

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

• Deficiency found before patient use: usually does not require an adverse-event report because no patient exposure occurred.
• Event caused solely by the patient’s condition: may not be reportable if the device did not contribute.
• Malfunction protection operated correctly: generally exempt when the device’s safety mechanism worked as intended and prevented harm.

CIMA P3 topics

• IT governance and systems strategy
• Systems development and implementation
• Change and project governance
• Strategic and business risk

• A — Plan for new systems: The committee should help identify and prioritise systems requirements and ensure planned systems support organisational needs.
• D — Consider competitive issues: New information systems may affect Y’s competitive position, service quality and efficiency. These strategic implications should be considered.
• E — Ensure the system meets company goals: This is a key governance responsibility. The committee should ensure the project remains aligned with Y’s objectives and delivers business value.

• B — Develop new systems: Detailed system development should be performed by IT specialists and project teams, not the steering committee.
• C — Manage the project: The project manager should handle day-to-day project management. The steering committee should provide oversight, challenge and key decisions, rather than manage daily activities.

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

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

• ?? ?? ?? ??
• ?? NFS ?? SMB ?? ??
• ?? ???? ???
• ?? IP ??? ???? ?? ???
• ??? ?? ???? ?????

• B: ????? NFS ? Snowball Edge? ?? ?? ? AWS? ?? ? S3
• D: ????? NFS ? ????/Direct Connect ? File Gateway ? S3

• Early units show relatively large time savings.
• Later units still take less time, but the reduction becomes progressively smaller.
• The curve therefore becomes flatter as production approaches 256 units.

• B: The reduction is not constant; learning normally diminishes over time.
• C: Time does not reduce at an increasing rate.
• D: A steady state may eventually be reached, but the question concerns the first 255 units while learning is still occurring.

• desktopwidth:i:1280
• desktopheight:i:1024

• Connection information: Controls connection-related settings, not the desktop resolution.
• Scaling plan: Controls when session hosts start, stop, or scale based on demand.
• Session behaviour: Controls behavior such as disconnect or logoff handling.
• Display settings: Specifically controls RDP display properties, making it the appropriate choice.

• Identity: User-assigned managed identity

• Authorization: Azure RBAC

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.

• Customers may boycott V’s products.
• Supermarket customers may stop buying from V.
• Investors may view V as having higher legal, ethical and reputational risk.
• V could face fines, lawsuits, contract losses and higher costs.
• Expected future profits may fall.

• Third-party enterprise application with embedded AI: The provider manages most security controls. The customer mainly manages users, data, and configuration.
• Application using an existing third-party FM: The customer controls the application and its inputs/outputs, but the provider controls the underlying model and infrastructure.
• Fine-tuning a third-party FM: The customer has additional responsibility for training data, data protection, and model behavior, but still depends on the provider’s base model and platform.
• Building and training a model from scratch: The customer controls the model, training data, application, deployment, and many security safeguards. This creates the greatest security ownership.

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

• CIA: Confidentiality, integrity, and availability—the core security objectives.
• ACL: Access Control List; rules that permit or deny traffic or access.
• PEM: A format and standard commonly associated with encoded certificates and keys.

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

• Shared capacity

• Fabric capacity — F SKUs

• Fabric trial capacity

• Existing Power BI Premium — P SKUs

• Annual interest payments net of tax relief (A): future cash outflows for the issuer.
• Redemption value (B): the final cash outflow when the bond is redeemed.
• Market value now (C): the cash proceeds received now, acting as the initial cash flow in the IRR calculation.

• C: Develop the rule in the Rules Editor, define the events, match, and condition sections, then use the test rule feature. This directly validates the YARA-L rule without enabling it in production.
• A: UDM Search can help investigate data and refine filters, but it does not fully test YARA-L logic—especially complex event joins, match windows, and conditions.

• Partners first log in to the corporate portal, which uses the shared SAML Identity Provider.
• When they select a Salesforce link, the IdP can send a SAML assertion directly to Salesforce.
• Salesforce validates the assertion and grants access to the Partner Community without requiring another login. This is IdP-initiated SSO because authentication begins outside Salesforce.

• SP-initiated SSO starts when Salesforce sends an authentication request to the IdP. That would be appropriate if users began by visiting Salesforce.
• The Web Server and User Agent OAuth flows are for OAuth authorization, not browser-based SAML federation between an IdP and Salesforce.

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

• Installing software
• Applying configuration changes
• Calling PowerShell scripts
• Running setup or customization commands

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

• GPO logon script: Runs only when a user logs on and depends on domain/GPO processing.
• GPO startup script: Runs during startup, but requires the VM to be domain joined and receives the applicable GPO.
• Place scripts in a VHD: Merely makes the scripts available; it does not automatically execute them.

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()

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

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

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

1. Wireless AP

1. Router

1. Firewall

1. Device placement

• Tracking who accessed or changed customer information
• Detecting unauthorized activity
• Supporting accountability and investigations
• Providing evidence for compliance and incident response

• Single sign-on not enabled: SSO improves convenience and centralized authentication, but it is not essential for access control.
• Complex passwords not required: This weakens authentication, but other controls may reduce the risk.
• Security baseline not consistently applied: A concern, but it is less specific and less immediately damaging than having no activity records at all.

• Box 1: No — The rule requires user.department to equal Engineering. Engineer does not match, so User1 is not in AU1. Admin1 cannot reset User1’s password.
• Box 2: No — Admin1’s role is scoped to AU1 and cannot manage users outside that AU.
• Box 3: Yes — Admin2 is a Global Administrator and can reset User3’s password.

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

• Third-party attestation: Provides independent validation, but is typically periodic and performed by an external party.
• Penetration testing: Simulates attacks to identify exploitable vulnerabilities; it does not primarily track compliance.
• Vulnerability scans: Identify technical weaknesses, but do not provide a detailed review of procedures or compliance activities.

• A — Use getRecordTypeInfosByDeveloperName()

apex 
  Id rtId = Schema.SObjectType.Account 
      .getRecordTypeInfosByDeveloperName() 
      .get('Business_Account') 
      .getRecordTypeId();

• C — Query the RecordType object

apex 
  RecordType rt = [ 
      SELECT Id 
      FROM RecordType 
      WHERE SObjectType = 'Account' 
      AND Name = 'Business Account' 
      LIMIT 1 
  ];

• B: An outbound SOAP call is unnecessary and inefficient.
• D: Hardcoding an ID is not dynamic, and IDs can differ between orgs.

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

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

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

• Run the backup with WITH CHECKSUM
• Store the backup on an SMB network share

sql 
BACKUP DATABASE DB1 
TO DISK = '\\FileServer\SqlBackups\DB1_full.bak' 
WITH CHECKSUM;

• DMS does not create the SQL Server backups for you.
• You must provide a valid full database backup.
• You must continue taking transaction log backups while the source database remains online.
• The full backup and subsequent log backups must be available in the SMB share that DMS can access.
• WITH CHECKSUM enables backup checksum validation, helping detect backup corruption.

• Enforce organizational rules, such as allowed regions or required tags
• Audit resources for compliance
• Deny noncompliant deployments
• Aggregate compliance results across subscriptions

• Data Cloud combines data from multiple systems.
• It resolves and organizes that data into a unified customer view.
• That unified view enables downstream actions such as personalized campaigns, segmentation, analytics, and activation.

• A = core platform value
• D = a resulting business use case or benefit

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

• WPA3: Secures wireless traffic but does not normally verify whether someone has paid.
• PSK: A shared Wi-Fi password gives access to anyone who knows it; it cannot easily validate individual receipts.
• IEEE 802.1X: Provides user/device authentication, commonly through an authentication server, but is excessive and not designed specifically for a simple receipt-based guest-access workflow.

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

Step 1: Calculate the rights issue price

Step 2: Calculate the number of new shares

Step 3: Calculate the value after the issue and project

• Rights issue proceeds: $21.6m
• Project NPV: $5m

Step 4: Calculate the theoretical ex-rights price

• B. Conditional access policies

• D. Additional authentication factors

• Disciplinary actions: Punish users but do not prevent credential-based attacks.
• More regular account audits: Useful for finding inactive or excessive accounts, but less direct for stopping unauthorized logins.
• Content filtering: Primarily controls web or email content, not authentication.
• Review of permissions: Reduces privilege but may not stop unauthorized account access.

• Share files with the wrong people
• Use public links unnecessarily
• Fail to classify sensitive data
• Upload data to unauthorized services
• Misunderstand company sharing policies

• A — Step-up authentication: Helps protect administrator accounts, but does not directly address improper file sharing by users.
• C — Password complexity: Helps reduce password attacks, not accidental data disclosure.
• D — Mobile device management: Secures managed mobile devices, but does not directly control file-sharing behavior across the organization.

• A — Use a custom controller: An Apex class can contain the page’s logic.
• C — Use a standard controller with extensions: The standard controller provides basic CRUD behavior, while an extension adds custom logic.
• E — Use a standard controller: Useful when the page works mainly with one Salesforce object and needs standard functionality.

• A page with no controller for static or controller-free content.
• A custom controller with extensions; extensions are not limited only to standard controllers.

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

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

• Reduce the training data: Usually makes overfitting worse.
• Add hyperparameters: Hyperparameters already control training; simply adding them does not solve the problem. Proper tuning could help, but that is not what the option states.
• Increase training time: More training can worsen overfitting if the model is already memorizing the training data.

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

1. Wireless AP

1. Router

1. Firewall

1. Device placement