PEOPLECERT PRINCE2 Agile Practitioner Exam Prep
PRINCE2 Agile Practitioner Project Management (Page 2 )

• AWS Audit Manager continuously collects evidence from AWS services and helps assess whether workloads comply with regulatory frameworks and internal policies. It can produce audit-ready reports.
• AWS Config records resource configurations and evaluates them against compliance rules. For example, it can check whether encryption, logging, or access settings meet company requirements.

• Amazon Inspector identifies software vulnerabilities and unintended network exposure, not general policy or regulatory compliance.
• Amazon CloudWatch monitors metrics, logs, and operational events, but is not primarily a compliance assessment service.
• AWS CloudTrail records API activity for auditing and investigation. It supports compliance, but does not itself provide the structured compliance assessment capabilities of Audit Manager and Config.

• Digitally signing the software: Verifies authenticity and integrity. It does not hide how the software works.
• Limiting third-party libraries: May reduce dependencies and attack surface, but does not directly prevent reverse engineering.
• Using compile flags: Some compiler options can remove debugging information or optimize code, which may provide limited protection, but this is not the primary technique identified for preventing reverse engineering.

• IaaS provides virtualized infrastructure, including VMs, disks, and networking. You manage the guest operating system and software installed on the VM.
• PaaS provides a managed platform for deploying applications without managing the underlying VMs or operating systems. Examples include Azure App Service and Azure Functions.

• BIOS language support: Useful for usability, but not whether the PC can operate electrically.
• Supply chain security: Concerns procurement and hardware trust, not deployment across countries.
• Power efficiency: Important for energy usage, but it does not ensure compatibility with local power systems.

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• The target API uses HTTPS, so Mule must validate the server’s TLS certificate.
• The TLS configuration is set to None, meaning no custom truststore is configured.
• Mule therefore uses the JRE’s default truststore to determine whether the target certificate is trusted.
• If the issuing CA certificate is in that truststore, the TLS handshake can succeed.
• If it is absent—or the certificate is otherwise invalid—the request fails with a TLS/handshake error.

• Guiding principles
• Governance
• Service value chain
• Practices
• Continual improvement

• Guiding principles: Recommendations that guide decisions and actions; they do not describe the entire system.
• Four dimensions: Perspectives used to ensure a balanced approach to service management.
• Service relationship: Describes cooperation between a service provider and service consumer, rather than the whole value-creation system.

• Accept: Acknowledge the risk and choose not to take 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 condition that creates the risk.

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

• C — Schema.describeSObjects(new String[]{myObject})[0].fields.getMap()

• D — Schema.getGlobalDescribe().get(myObject).getDescribe().fields.getMap()

• A: sObjectType is not used this way, and fieldSet() is not the appropriate method for retrieving all fields.
• B: mySObject.myObject is not valid dynamic Apex syntax.

• SAMLRequest: the SAML authentication request
• RelayState: the original destination or application state

• RedirectURL: not the standard SAML parameter for preserving the original request.
• DisplayState: not a standard SAML SSO parameter.
• StartURL: Salesforce-related terminology, but not the standard parameter used in this SAML exchange.

• Due Date
• Order Date
• Delivery Date

DAX 
Order Date = 'Due Date' 
Delivery Date = 'Due Date'

• Due Date[Date] ? Sales[Due Date]
• Order Date[Date] ? Sales[Order Date]
• Delivery Date[Date] ? Sales[Delivery Date]

• A single Construction Job can use multiple Machinery records.
• A single Machinery record may be used on multiple Construction Jobs.
• This is a many-to-many relationship, which Salesforce models using a junction object.
• The junction object can contain fields such as:

• Master-detail to Machinery
• Master-detail to Construction Job
• Date and cost fields

• A — Increasing the minimum password length to 14 characters: Longer passwords have more possible combinations, making them harder to guess or crack through brute force.
• F — Requiring at least one special character: This increases password complexity and expands the possible character combinations.

• MD5 to SHA-512: Improves password-hash resistance, but does not stop users from choosing easy-to-guess passwords. Also, modern systems should use a password-specific hashing algorithm such as bcrypt, scrypt, or Argon2.
• Increasing maximum age to 120 days: Leaves weak passwords in use longer.
• Reducing minimum length to 10: Makes guessing easier.
• Reducing minimum age to zero: Allows immediate password changes but does not make the password itself harder to guess.

• Inherent risk: Risk that exists before controls are implemented.
• Avoided risk: Risk eliminated by choosing not to perform the risky activity.
• Operational risk: Risk arising from failures in processes, people, systems, or daily operations.

• Actual filename: Document.xml.txt
• Explorer displays: Document.xml
• File type: Text Document (.txt)

text 
Document.txt ? Document.xml

• Batch processing, such as scheduled data transformations
• Streaming processing, such as continuously ingesting events

• Manipulating data with multiple languages: Mainly a benefit of Databricks and Spark.
• Real-time notebook collaboration: A workspace/notebook feature.
• Alerts for query failures: A Databricks SQL or job-monitoring feature.
• Distributing complex operations: Primarily a Spark compute capability.

• A — Custom Button: A button can launch a flow, typically by passing the flow’s URL and record context.
• D — From a Process: A Process can invoke a flow using an Apex action configured for flow invocation. However, this is automation-triggered, not directly accessed by a user.
• B — Quick Action: In current Salesforce functionality, a Flow Quick Action can launch a screen flow directly from a record page. This makes B a valid modern method.
• C — Visual Workflow Launcher: This is not generally listed as a standard access method in current Salesforce terminology; Salesforce commonly uses the Flow component on Lightning pages instead.

1. Selling price per unit: $750
2. Required annual return:

1. Required profit per unit:

1. Target cost per unit:

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• administrators — Full access to switch configuration and REST API functions; excessive for this requirement.
• sysadmin — Intended for highly privileged system administration, not basic monitoring.
• helpdesk — More limited and focused on troubleshooting/support functions; it does not match the stated default role and level-1 requirement as directly.

• Goal: Identify the host that originated the infection, then label each remaining host as infected or clean based on log evidence.

• Logs to review (across hosts and firewall):

• How to identify the origin:

• How to classify other hosts:

• Quick tip: use the Reset All option if you want to re-run the scenario and practice again.

1. Get Data ? Folder in Power BI Desktop.
2. In Power Query Editor, expand the Attributes column to expose metadata such as hidden status and other file attributes.
3. Remove the Content column (and any other data columns you do not need).

• Name
• Extension
• Date accessed
• Date modified
• Folder Path
• Attributes
• Content

• Basic: Self-help only; no technical support or design assessment.
• Developer/Standard: Technical support, but generally not the full proactive architecture guidance required here.
• Professional Direct: Includes proactive guidance and architecture recommendations.
• Premier: Also supports this, but is not the minimum-cost option.

• A — IDS attack signatures: An IDS generally detects suspicious network activity but does not necessarily scan uploaded PDF files or prevent them from being accepted.
• C — Load balancer: Distributes traffic among servers; it does not inspect files for malware.
• D — WAF command-injection blocking: A WAF can help block web attacks such as command injection, SQL injection, and cross-site scripting, but this option does not specifically address malicious PDF uploads.

1. Start with the Customer table.
2. Use Merge Queries and select the Address table.
3. Match Customer[Address ID] to Address[Address ID].
4. Use a Left Outer join so every customer is retained.
5. Expand only City, State/Region, and Country.

• Append adds rows vertically; it is for stacking similarly structured tables.
• Group By summarizes rows and does not retrieve address columns.
• Transpose swaps rows and columns and is unrelated to table relationships.

• Review iteration length: Changing duration does not resolve unclear requirements.
• Limit work in progress: Useful when excessive multitasking is the problem, but it does not directly clarify requirements.
• Review individual performance: The issue is a process and backlog-quality problem, not necessarily an individual performance problem.

• A — Reports: Reports are informational and don’t enforce access during an SSO transaction.
• B — Apex trigger and Permission Sets: A trigger could update permissions when a Case changes, but this creates synchronization and timing issues. It also changes Salesforce permissions rather than making a direct, real-time decision for the external system.
• C — Custom SAML JIT Provisioning: JIT provisioning is primarily for creating or updating users at login. It isn’t the appropriate mechanism for dynamically querying business records and deciding whether access should be granted.
• D — Connected App Handler: Designed for custom, programmatic control during connected-app authentication and authorization. Apex can check the user’s current open classified cases and permit or reject the SSO request.

• User1 can sign in because the account is cloud-only. It does not depend on the on-premises domain.
• User3 can sign in because the account uses Password Hash Synchronization (PHS). Azure AD has a synchronized password hash and can validate the sign-in even when connectivity to on-premises Active Directory is unavailable.
• User2 cannot sign in because the account relies on Pass-through Authentication (PTA). PTA sends the authentication request to an on-premises PTA agent, which must contact a domain controller. With the internet connection from on-premises lost, that validation cannot occur.

• A. Modify CommunitiesSelfRegController

• C. Configure Communities registration to use a custom Visualforce page

• B. Modify the self-registration trigger — There is no standard “self-registration trigger” intended for this configuration. The registration logic is handled by the Visualforce controller.
• D. Configure a custom Apex controller — The standard approach is to modify the provided CommunitiesSelfRegController, rather than simply selecting a separate controller configuration.

• Restarting the device: May fix software glitches, but would not usually make cable orientation matter.
• Swollen battery: A safety concern, but it would not typically cause recognition only in one cable orientation.
• Failing cable: Possible, but less likely because the problem occurs with this particular device and not other devices of the same type.

• Answer: No

• Why: Using several Azure AD directories (tenants) would create separate identity stores for each division, which significantly increases administrative overhead. You’d need cross-tenant access management, separate governance, and duplicated admin efforts, which goes against the goal of minimizing administrative work.

• How to meet the goal instead:

• Developed and maintained independently
• Deployed without changing the entire application
• Scaled separately based on demand
• More resilient when another service has problems

• A: Functional testing is useful, but it is not the main practice described.
• B: Automation helps deployment, but the scenario focuses on architectural decomposition.
• C: Multiple locations improve availability, not application modularity.

• Multi-pass wipe: Overwrites the drive’s existing data multiple times, making recovery much more difficult while preserving the drive’s functionality.
• Single-pass wipe: May be sufficient in some modern sanitization standards, but is presented here as less secure than multiple overwrites.
• Degaussing: Uses a strong magnetic field to disrupt data. It can render the drive unusable or unreliable, reducing its resale value.
• Pinning: Is not an appropriate data-sanitization method.

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

• Coordinate and manage the assessment team
• Assign assessment activities
• Direct interviews, examinations, and tests
• Ensure the assessment follows the CAP

• Answer key: Lead Assessor — likely wrong
• CAP-based answer: C3PAO

• A: Security groups do not control traffic to an S3 gateway endpoint in this way. Gateway endpoints are configured through route tables.
• B: An S3 bucket policy may be needed for authorization, but the error specifically indicates a connectivity or endpoint-routing problem.
• C: Glue connection settings do not require a fully qualified domain name to resolve this endpoint issue.

• A larger question bank with verified answers
• Explanations tied to ISACA exam domains
• Current content aligned with the exam blueprint
• Useful review or progress features

Why

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

Why the other options are less suitable

• GPO logon script: Runs only when a user logs on and may not run during initial VM provisioning.
• GPO startup script: Can work, but requires the VM to be joined to the domain and the policy to be applied. It is also normally evaluated at each startup.
• Place scripts in a VHD: Merely placing scripts on a disk does not cause them to execute.

• Conserve public IPv4 addresses: IPv4 addresses are limited, so many internal devices share a smaller number of public addresses through NAT.
• Reduce direct exposure: Private addresses are not directly routable from the public Internet, which helps reduce unsolicited access to internal devices.

• Port 515: LPD/LPR line-printer service
• Port 631: IPP — Internet Printing Protocol
• Port 9100: JetDirect/RAW printing, commonly used by network printers

• Linux machine: Linux could run these services, but the three printer-specific ports strongly indicate a printer.
• Router: Routers may use Telnet and HTTP, but normally would not expose ports 515, 631, and 9100 together.
• Windows machine: Windows can share printers, but this particular service combination is more characteristic of a network printer’s embedded operating system.

• Use one Azure AD directory for the organization.
• Separate divisions with subscriptions and/or resource groups.
• Assign each division’s administrator appropriate Azure role-based access control (RBAC) permissions, scoped to their subscription or resource group.

• Updating the CRL: Revokes compromised certificates, but does not fix the CA flaw that allowed them to be created.
• Changing passwords: May be necessary if accounts were compromised, but it does not address the certificate-generation vulnerability.
• Implementing SOAR: Improves security automation and response; it does not remediate the underlying PKI weakness.

• tag=Priv searches the tag field for values beginning with Priv. The wildcard can match the remaining characters, so it matches Privileged.
• tag=Priv would search for the exact tag Priv, not Privileged.
• tag=priv* uses lowercase priv; tag matching is treated as case-sensitive here, so it may not match the tag Privileged.
• tag=privileged uses the wrong capitalization for the exact tag.

• Answer: C – netstat -an

• netstat -an lists all active connections and listening ports with numeric addresses, without resolving names. This lets you spot DoS patterns such as a flood of connections to a specific port or many connections from a single or few IPs.
• The other options don’t help as directly:

• Windows: netstat -an and look for numerous ESTABLISHED connections to a service or many SYNs to a port.
• Filter by port, e.g., netstat -an | findstr :80, or on Linux: ss -tunap | grep ':80'.

• Netstat provides a snapshot. DoS detection often benefits from continuous monitoring, flow data, and IDS/IPS logs.

• The Balanced Scorecard translates an organization’s vision and strategy into a set of concrete objectives and metrics across four perspectives (financial, customer, internal processes, learning & growth). This framework explicitly links IT goals to business goals and provides a way to measure and monitor alignment over time.

• Enterprise architecture (EA): Great for governance, standards, and roadmaps to ensure IT assets support business needs, but it’s more about structure and alignment at design time rather than directly measuring ongoing alignment of goals.
• KPIs: Useful metrics, but they don’t by themselves provide a full framework to ensure IT goals are aligned with organizational strategy.
• Enterprise dashboard: A visualization tool for metrics; it helps report status but doesn’t inherently establish or assess alignment.

• A private IP address on the virtual network
• A public IP address associated with its IP configuration

• Secret scope: A named container that groups related secrets and defines access permissions. Example: finance-prod.
• Secret key: The name of an individual secret stored inside that scope. Example: db-password.

text 
Scope: finance-prod 
  Key: db-username 
  Key: db-password

python 
dbutils.secrets.get( 
    scope="finance-prod", 
    key="db-password" 
)

• Creating and managing users and roles
• Granting and revoking roles and privileges
• Managing access-control responsibilities

• SYSADMIN: Manages warehouses, databases, schemas, and other objects—not primarily users and roles.
• PUBLIC: Automatically granted to every user; it is not an administrative role.
• ACCOUNTADMIN: Has the highest level of access, but should be reserved for account-level administration and emergencies rather than routine security tasks.